linux-kernel - Re: [syzbot] [mm?] WARNING: locking bug in __set_page

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aOyyER1uSsPl5b7a@localhost.localdomain>
Date: Mon, 13 Oct 2025 10:02:25 +0200
From: Oscar Salvador <osalvador@...e.de>
To: Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
	syzbot <syzbot+8259e1d0e3ae8ed0c490@...kaller.appspotmail.com>,
	Johannes Weiner <hannes@...xchg.org>,
	Brendan Jackman <jackmanb@...gle.com>,
	LKML <linux-kernel@...r.kernel.org>, linux-mm <linux-mm@...ck.org>,
	Michal Hocko <mhocko@...e.com>,
	Network Development <netdev@...r.kernel.org>,
	Suren Baghdasaryan <surenb@...gle.com>,
	syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
	Vlastimil Babka <vbabka@...e.cz>, ziy@...dia.com,
	bpf <bpf@...r.kernel.org>
Subject: Re: [syzbot] [mm?] WARNING: locking bug in __set_page_owner (2)

On Thu, Oct 09, 2025 at 05:26:21PM -0700, Alexei Starovoitov wrote:
> On Thu, Oct 9, 2025 at 4:52 PM Andrew Morton <akpm@...ux-foundation.org> wrote:
> >
> > On Thu, 09 Oct 2025 09:45:33 -0700 syzbot <syzbot+8259e1d0e3ae8ed0c490@...kaller.appspotmail.com> wrote:
> >
> > > Hello,
> > >
> > > syzbot found the following issue on:
> > >
> > > HEAD commit:    2c95a756e0cf net: pse-pd: tps23881: Fix current measuremen..
> > > git tree:       net
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=16e1852f980000
> > > kernel config:  https://syzkaller.appspot.com/x/.config?x=5bcbbf19237350b5
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=8259e1d0e3ae8ed0c490
> > > compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
> > >
> > > Unfortunately, I don't have any reproducer for this issue yet.
> > >
> > > Downloadable assets:
> > > disk image: https://storage.googleapis.com/syzbot-assets/8272657e4298/disk-2c95a756.raw.xz
> > > vmlinux: https://storage.googleapis.com/syzbot-assets/4e53ba690f28/vmlinux-2c95a756.xz
> > > kernel image: https://storage.googleapis.com/syzbot-assets/6112d620d6fc/bzImage-2c95a756.xz
> > >
> > > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > > Reported-by: syzbot+8259e1d0e3ae8ed0c490@...kaller.appspotmail.com
> >
> > At 2c95a756e0cf, page_owner.c hasn't been modified in a couple of years.
> >
> > How can add_stack_record_to_list()'s spin_lock_irqsave() be "invalid
> > wait context"?  In NMI, yes, but the trace doesn't indicate that we're
> > in an NMI.
> >
> > Confused.  I'm suspecting BPF involvement.  Cc'ed for help, please.
> 
> The attached patch should fix it.
> There are different options, but this one is the simplest.

Seems quite trivial to backport, so:

Reviewed-by: Oscar Salvador <osalvador@...e.de>




-- 
Oscar Salvador
SUSE Labs