From: syzbot <syzbot+2f73ed585f115e98aee8@syzkaller.appspotmail.com>
To: linkinjeon@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, namjae.jeon@samsung.com,
sj1557.seo@samsung.com, syzkaller-bugs@googlegroups.com,
torvalds@linux-foundation.org
Subject: Re: [syzbot] [exfat?] INFO: task hung in exfat_write_inode
Date: Wed, 29 Nov 2023 13:42:04 -0800 [thread overview]
Message-ID: <000000000000f5144d060b5167d8@google.com> (raw)
In-Reply-To: <000000000000db858c05f06f30b0@google.com>
syzbot has bisected this issue to:
commit 907fa893258ba6076f5fff32900a461decb9e8c5
Author: Namjae Jeon <namjae.jeon@samsung.com>
Date: Thu May 21 23:10:10 2020 +0000
exfat: add the dummy mount options to be backward compatible with staging/exfat
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=138aca9ae80000
start commit: f9ff5644bcc0 Merge tag 'hsi-for-6.2' of git://git.kernel.o..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=104aca9ae80000
console output: https://syzkaller.appspot.com/x/log.txt?x=178aca9ae80000
kernel config: https://syzkaller.appspot.com/x/.config?x=c163713cf9186fe7
dashboard link: https://syzkaller.appspot.com/bug?extid=2f73ed585f115e98aee8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11d6fe00480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15d2fc63880000
Reported-by: syzbot+2f73ed585f115e98aee8@syzkaller.appspotmail.com
Fixes: 907fa893258b ("exfat: add the dummy mount options to be backward compatible with staging/exfat")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-11-29 21:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 18:53 [syzbot] [exfat?] INFO: task hung in exfat_write_inode syzbot
2023-11-29 21:42 ` syzbot [this message]
2023-11-30 7:28 ` [syzbot] " syzbot
2023-11-30 7:55 ` syzbot
2023-11-30 8:43 ` syzbot
2023-12-21 4:50 ` Lizhi Xu
2023-12-21 5:18 ` [syzbot] [exfat?] INFO: " syzbot
2023-12-21 6:11 ` Lizhi Xu
2023-12-21 6:35 ` [syzbot] [exfat?] INFO: " syzbot
[not found] <20231130072806.1240587-1-lizhi.xu@windriver.com>
2023-11-30 7:45 ` syzbot
[not found] <20231130075546.1506719-1-lizhi.xu@windriver.com>
2023-11-30 8:26 ` syzbot
[not found] <20231130084311.2983367-1-lizhi.xu@windriver.com>
2023-11-30 9:04 ` syzbot
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=000000000000f5144d060b5167d8@google.com \
--to=syzbot+2f73ed585f115e98aee8@syzkaller.appspotmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=sj1557.seo@samsung.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox