From: syzbot <syzbot+837bcd54843dd6262f2f@syzkaller.appspotmail.com>
To: axboe@kernel.dk, chandan.babu@oracle.com, djwong@kernel.org,
hch@lst.de, 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: Sat, 17 Aug 2024 21:36:01 -0700 [thread overview]
Message-ID: <000000000000c9eee7061fedbac5@google.com> (raw)
In-Reply-To: <0000000000008905bf061fc61371@google.com>
syzbot has bisected this issue to:
commit 3eb96946f0be6bf447cbdf219aba22bc42672f92
Author: Christoph Hellwig <hch@lst.de>
Date: Wed May 24 06:05:38 2023 +0000
block: make bio_check_eod work for zero sized devices
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=178bfdcb980000
start commit: 85652baa895b Merge tag 'block-6.11-20240824' of git://git...
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=144bfdcb980000
console output: https://syzkaller.appspot.com/x/log.txt?x=104bfdcb980000
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
Reported-by: syzbot+837bcd54843dd6262f2f@syzkaller.appspotmail.com
Fixes: 3eb96946f0be ("block: make bio_check_eod work for zero sized devices")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-08-18 4:36 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 [this message]
2024-08-19 22:16 ` Dave Chinner
2025-06-25 21:10 ` syzbot
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=000000000000c9eee7061fedbac5@google.com \
--to=syzbot+837bcd54843dd6262f2f@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=chandan.babu@oracle.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--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;
as well as URLs for NNTP newsgroup(s).