From: syzbot <syzbot+6f75830acb2e4cdc8e50@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, brauner@kernel.org,
hirofumi@mail.parknet.co.jp, linkinjeon@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
sj1557.seo@samsung.com, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk, willy@infradead.org
Subject: Re: [syzbot] [exfat?] INFO: task hung in fat_write_inode
Date: Fri, 03 Nov 2023 05:27:04 -0700 [thread overview]
Message-ID: <0000000000003c325306093e9f25@google.com> (raw)
In-Reply-To: <000000000000af7bd706084b7cb2@google.com>
syzbot has bisected this issue to:
commit fb96458067a8043c256befe4bfe4fb3ebc81de1b
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date: Mon Oct 16 20:10:48 2023 +0000
buffer: return bool from grow_dev_folio()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=154b4ef7680000
start commit: 2dac75696c6d Add linux-next specific files for 20231018
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=174b4ef7680000
console output: https://syzkaller.appspot.com/x/log.txt?x=134b4ef7680000
kernel config: https://syzkaller.appspot.com/x/.config?x=6f8545e1ef7a2b66
dashboard link: https://syzkaller.appspot.com/bug?extid=6f75830acb2e4cdc8e50
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=148fed9d680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1019f523680000
Reported-by: syzbot+6f75830acb2e4cdc8e50@syzkaller.appspotmail.com
Fixes: fb96458067a8 ("buffer: return bool from grow_dev_folio()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-11-03 12:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 10:22 [syzbot] [exfat?] INFO: task hung in fat_write_inode syzbot
2023-11-03 12:27 ` 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=0000000000003c325306093e9f25@google.com \
--to=syzbot+6f75830acb2e4cdc8e50@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.