[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Zi7GDznXWDsW4CsH@dread.disaster.area>
Date: Mon, 29 Apr 2024 07:56:31 +1000
From: Dave Chinner <david@...morbit.com>
To: syzbot <syzbot+4a799ff34dbbb5465776@...kaller.appspotmail.com>
Cc: chandan.babu@...cle.com, djwong@...nel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-xfs@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [xfs?] possible deadlock in xfs_qm_flush_one
On Wed, Apr 17, 2024 at 11:42:20AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 9ed46da14b9b Add linux-next specific files for 20240412
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=11a4a1dd180000
> kernel config: https://syzkaller.appspot.com/x/.config?x=7ea0abc478c49859
> dashboard link: https://syzkaller.appspot.com/bug?extid=4a799ff34dbbb5465776
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
#syz dup: possible deadlock in xfs_ilock_data_map_shared
--
Dave Chinner
david@...morbit.com
Powered by blists - more mailing lists