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

Message-ID: <aV0OE0PBhxjuPU8p@nidhogg.toxiclabs.cc>
Date: Tue, 6 Jan 2026 14:35:39 +0100
From: Carlos Maiolino <cem@...nel.org>
To: Dave Chinner <david@...morbit.com>
Cc: Christoph Hellwig <hch@...radead.org>, 
	syzbot <syzbot+c628140f24c07eb768d8@...kaller.appspotmail.com>, 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 08:54:37PM +1100, Dave Chinner wrote:
> 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.

FWIW iomap patches don't go through xfs tree.

Patch is here, in linux-next since next-20251216
https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git/commit/?id=ed61378b4dc63efe76cb8c23a36b228043332da3

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