From: Vlastimil Babka <vbabka@suse.cz>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: syzbot <syzbot+8259e1d0e3ae8ed0c490@syzkaller.appspotmail.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Brendan Jackman <jackmanb@google.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Michal Hocko <mhocko@suse.com>,
Network Development <netdev@vger.kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
ziy@nvidia.com, bpf <bpf@vger.kernel.org>
Subject: Re: [syzbot] [mm?] WARNING: locking bug in __set_page_owner (2)
Date: Mon, 13 Oct 2025 10:10:59 +0200 [thread overview]
Message-ID: <32a23856-ffaa-4d41-b77f-fa0306042621@suse.cz> (raw)
In-Reply-To: <CAADnVQKkLyJ0cbLet3q3X+X70FPAejcqTxP66d82WTO82c16rw@mail.gmail.com>
On 10/10/25 03:02, Alexei Starovoitov wrote:
> On Thu, Oct 9, 2025 at 5:41 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>> Seems 6.18 will need this. Do you think it is needed in earlier kernel
>> versions?
>
> Maybe. I need to study the git history of that code to see
> whether it's a new path or I simply missed it earlier.
I would add the following, which means 6.15. Maybe there were no users
immediately that would trigger it, but should be proper. The only non-EOL
stable is 6.17 anyway, but might help others backporting.
Fixes: 97769a53f117 ("mm, bpf: Introduce try_alloc_pages() for opportunistic
page allocation")
Acked-by: Vlastimil Babka <vbabka@suse.cz>
next prev parent reply other threads:[~2025-10-13 8:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 16:45 syzbot
2025-10-09 23:52 ` Andrew Morton
2025-10-10 0:26 ` Alexei Starovoitov
2025-10-10 0:41 ` Andrew Morton
2025-10-10 1:02 ` Alexei Starovoitov
2025-10-13 8:10 ` Vlastimil Babka [this message]
2025-10-13 8:02 ` Oscar Salvador
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=32a23856-ffaa-4d41-b77f-fa0306042621@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=netdev@vger.kernel.org \
--cc=surenb@google.com \
--cc=syzbot+8259e1d0e3ae8ed0c490@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=ziy@nvidia.com \
/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