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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20241105090048.GZ9767@noisy.programming.kicks-ass.net>
Date: Tue, 5 Nov 2024 10:00:48 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: syzbot <syzbot+56dc65adbd1d2ae1f844@...kaller.appspotmail.com>,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	syzkaller-bugs@...glegroups.com, Boqun Feng <boqun.feng@...il.com>
Subject: Re: [syzbot] [mm?] WARNING: locking bug in __set_page_owner

On Mon, Nov 04, 2024 at 07:33:45PM -0800, Andrew Morton wrote:
> On Sun, 03 Nov 2024 08:49:26 -0800 syzbot <syzbot+56dc65adbd1d2ae1f844@...kaller.appspotmail.com> wrote:
> 
> > Hello,
> > 
> > syzbot found the following issue on:
> 
> Help.  I don't understand this lockdep report. 
> add_stack_record_to_list() is taking spin_lock_irqsave(stack_list_lock)
> from within softirq. all seems well?

spinlock_t from hardirq context, which is not fine. Should be
raw_spinlock_t.

Anyway, I send a proposal for this one yesterday, and so far nobody
seems to have screamed murder, so I suppose I'll make it compiler and
send out proper.

https://lkml.kernel.org/r/20241104114506.GC24862@noisy.programming.kicks-ass.net

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ