From: syzbot <syzbot+b44399433a41aaed7a9f@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] Re: [syzbot] [xfs?] possible deadlock in xfs_qm_dqfree_one
Date: Mon, 18 Mar 2024 20:45:56 -0700 [thread overview]
Message-ID: <000000000000c846560613fb4fce@google.com> (raw)
In-Reply-To: <000000000000e981c10613fb227e@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: Re: [syzbot] [xfs?] possible deadlock in xfs_qm_dqfree_one
Author: david@fromorbit.com
On Mon, Mar 18, 2024 at 08:33:23PM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 906a93befec8 Merge tag 'efi-fixes-for-v6.9-1' of git://git..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=12d6ea6e180000
> kernel config: https://syzkaller.appspot.com/x/.config?x=5206351398500a90
> dashboard link: https://syzkaller.appspot.com/bug?extid=b44399433a41aaed7a9f
> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> Downloadable assets:
> disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-906a93be.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/f096ab7eaede/vmlinux-906a93be.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/52e0859d6157/bzImage-906a93be.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+b44399433a41aaed7a9f@syzkaller.appspotmail.com
#syz dup: [syzbot] [xfs?] possible deadlock in xfs_qm_dqget_cache_insert
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2024-03-19 3:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 3:33 [syzbot] [xfs?] possible deadlock in xfs_qm_dqfree_one syzbot
2024-03-19 3:45 ` syzbot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000c846560613fb4fce@google.com \
--to=syzbot+b44399433a41aaed7a9f@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox