From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: Oscar Salvador <osalvador@suse.de>
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: Tue, 19 Mar 2024 19:51:59 +0900 [thread overview]
Message-ID: <37cb2e7c-97f1-4179-a715-84cc02096083@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <ZfKgs9E2ozZER20D@localhost.localdomain>
On 2024/03/14 16:01, Oscar Salvador wrote:
> On Thu, Mar 14, 2024 at 06:47:43AM +0100, Oscar Salvador wrote:
>> 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.
>
> I already have the fix. I will do some more testing and then I will send
> it out.
OK. Please test your patch using
https://syzkaller.appspot.com/bug?extid=98c1a1753a0731df2dd4 .
next prev parent reply other threads:[~2024-03-19 10:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 23:42 Oscar Salvador
2024-03-13 23:46 ` Oscar Salvador
2024-03-14 3:01 ` Tetsuo Handa
2024-03-14 5:47 ` Oscar Salvador
2024-03-14 7:01 ` Oscar Salvador
2024-03-19 10:51 ` Tetsuo Handa [this message]
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=37cb2e7c-97f1-4179-a715-84cc02096083@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--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=osalvador@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox