From: Dave Chinner <david@fromorbit.com>
To: syzbot <syzbot+0260338e3eff65854d1f@syzkaller.appspotmail.com>
Cc: chandan.babu@oracle.com, djwong@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [xfs?] INFO: task hung in xfs_inodegc_flush
Date: Thu, 8 Feb 2024 07:54:43 +1100 [thread overview]
Message-ID: <ZcPuE4FL9bUu8h0Q@dread.disaster.area> (raw)
In-Reply-To: <00000000000088268a0610c6b3ae@google.com>
On Wed, Feb 07, 2024 at 12:44:21AM -0800, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 076d56d74f17 Add linux-next specific files for 20240202
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=173b568fe80000
> kernel config: https://syzkaller.appspot.com/x/.config?x=428086ff1c010d9f
> dashboard link: https://syzkaller.appspot.com/bug?extid=0260338e3eff65854d1f
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=148b3c9fe80000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13811004180000
.....
>
> If the report is already addressed, let syzbot know by replying with:
> #syz fix: exact-commit-title
#syz fix: workqueue: Fix pwq->nr_in_flight corruption in try_to_grab_pending()
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2024-02-07 20:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 8:44 [syzbot] [xfs?] INFO: task hung in xfs_inodegc_flush syzbot
2024-02-07 20:54 ` Dave Chinner [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=ZcPuE4FL9bUu8h0Q@dread.disaster.area \
--to=david@fromorbit.com \
--cc=chandan.babu@oracle.com \
--cc=djwong@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=syzbot+0260338e3eff65854d1f@syzkaller.appspotmail.com \
--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