From: syzbot <syzbot+837bcd54843dd6262f2f@syzkaller.appspotmail.com>
To: axboe@kernel.dk, cem@kernel.org, chandan.babu@oracle.com,
david@fromorbit.com, djwong@kernel.org, hch@lst.de,
john.g.garry@oracle.com, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [xfs?] INFO: task hung in xfs_buf_item_unpin (2)
Date: Wed, 25 Jun 2025 14:10:02 -0700 [thread overview]
Message-ID: <685c65aa.050a0220.2303ee.0098.GAE@google.com> (raw)
In-Reply-To: <0000000000008905bf061fc61371@google.com>
syzbot suspects this issue was fixed by commit:
commit b1e09178b73adf10dc87fba9aee7787a7ad26874
Author: John Garry <john.g.garry@oracle.com>
Date: Wed May 7 21:18:31 2025 +0000
xfs: commit CoW-based atomic writes atomically
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1078f70c580000
start commit: 85652baa895b Merge tag 'block-6.11-20240824' of git://git...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=92c0312151c4e32e
dashboard link: https://syzkaller.appspot.com/bug?extid=837bcd54843dd6262f2f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12350ad5980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=147927c5980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: xfs: commit CoW-based atomic writes atomically
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-06-25 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 5:17 [syzbot] [xfs?] INFO: task hung in xfs_buf_item_unpin (2) syzbot
2024-08-17 9:19 ` syzbot
2024-08-18 4:36 ` syzbot
2024-08-19 22:16 ` Dave Chinner
2025-06-25 21:10 ` syzbot [this message]
2025-06-26 7:33 ` John Garry
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=685c65aa.050a0220.2303ee.0098.GAE@google.com \
--to=syzbot+837bcd54843dd6262f2f@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=cem@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=john.g.garry@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@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