linux-kernel - Re: Re: [PATCH] mm: fix lockdep issues in writeback handling

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250902095250.1319807-1-nogikh@google.com>
Date: Tue,  2 Sep 2025 11:52:50 +0200
From: Aleksandr Nogikh <nogikh@...gle.com>
To: david@...hat.com
Cc: akpm@...ux-foundation.org, joannelkoong@...il.com, 
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, 
	linux-mm@...ck.org, m.szyprowski@...sung.com, mszeredi@...hat.com, 
	willy@...radead.org, syzkaller-bugs@...glegroups.com
Subject: Re: Re: [PATCH] mm: fix lockdep issues in writeback handling

Hi,

When can the patch be expected to reach linux-next?
Syzbot can't build/boot the tree for more than 12 days already :(

-- 
Aleksandr

On 27.08.25, David Hildenbrand wrote:
> On 26.08.25 15:09, Marek Szyprowski wrote:
> > Commit 167f21a81a9c ("mm: remove BDI_CAP_WRITEBACK_ACCT") removed
> > BDI_CAP_WRITEBACK_ACCT flag and refactored code that depend on it.
> > Unfortunately it also moved some variable intialization out of guarded
> > scope in writeback handling, what triggers a true lockdep warning. Fix
> > this by moving initialization to the proper place.
> 
> Nasty
> 
> > 
> > Fixes: 167f21a81a9c ("mm: remove BDI_CAP_WRITEBACK_ACCT")
> > Signed-off-by: Marek Szyprowski <m.szyprowski@...sung.com>
> > ---
> 
> Acked-by: David Hildenbrand <david@...hat.com>
> 
> -- 
> Cheers
> 
> David / dhildenb