All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oscar Salvador <osalvador@suse.de>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Lei Yang <leiyang@redhat.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Michal Hocko <mhocko@suse.com>, Vlastimil Babka <vbabka@suse.cz>,
	Marco Elver <elver@google.com>,
	Andrey Konovalov <andreyknvl@gmail.com>,
	Alexander Potapenko <glider@google.com>
Subject: Re: [PATCH] mm,page_owner: Fix recursion
Date: Thu, 14 Mar 2024 06:47:43 +0100	[thread overview]
Message-ID: <ZfKPf_pGxv-xtSPN@localhost.localdomain> (raw)
In-Reply-To: <2ff96a50-fc65-4e42-b15d-097c0f15a455@I-love.SAKURA.ne.jp>

On Thu, Mar 14, 2024 at 12:01:24PM +0900, Tetsuo Handa wrote:
> Maybe culprit for a page owner refcount bug reported at
> https://syzkaller.appspot.com/bug?id=8e4e66dfe299a2a00204ad220c641daaf1486a00 , for
> that commit went to next-20240214 and syzbot started failing to test since next-20240215 ?
> 
> Please send this patch to linux-next.git as soon as possible (or can someone experiencing
> this bug try booting linux-next.git with this patch applied, so that we can check whether
> syzbot can resume testing linux-next.git), and then send to linux.git together (so that
> various trees which depend on linux.git won't start failing to boot).

No, that is something else that I already started fixing a few days ago.
I think I will have the fix ready today.


-- 
Oscar Salvador
SUSE Labs

  reply	other threads:[~2024-03-14  5:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-13 23:42 [PATCH] mm,page_owner: Fix recursion Oscar Salvador
2024-03-13 23:46 ` Oscar Salvador
2024-03-14  3:01 ` Tetsuo Handa
2024-03-14  5:47   ` Oscar Salvador [this message]
2024-03-14  7:01     ` Oscar Salvador
2024-03-19 10:51       ` Tetsuo Handa
2024-03-15 13:07 ` Vlastimil Babka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZfKPf_pGxv-xtSPN@localhost.localdomain \
    --to=osalvador@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@gmail.com \
    --cc=elver@google.com \
    --cc=glider@google.com \
    --cc=leiyang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=vbabka@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.