linux-kernel - Re: [syzbot] [xfs?] possible deadlock in xfs

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: <aVzb3ZHsC6XXUV8i@dread.disaster.area>
Date: Tue, 6 Jan 2026 20:54:37 +1100
From: Dave Chinner <david@...morbit.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: syzbot <syzbot+c628140f24c07eb768d8@...kaller.appspotmail.com>,
	cem@...nel.org, linux-kernel@...r.kernel.org,
	linux-xfs@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [xfs?] possible deadlock in xfs_ilock (4)

On Tue, Jan 06, 2026 at 12:10:55AM -0800, Christoph Hellwig wrote:
> On Tue, Jan 06, 2026 at 10:15:32AM +1100, Dave Chinner wrote:
> > iomap: use mapping_gfp_mask() for iomap_fill_dirty_folios()
> 
> This looks good, but didn't we queue up Brian's fix to remove
> the allocation entirely by now?

No idea - I didn't see a fix in the XFS for-next or the VFS
7.20-iomap branches.  I've been on holidays for the past couple of
weeks so I'd kinda forgotten that we'd been through this a month
ago.

-Dave.
-- 
Dave Chinner
david@...morbit.com