From: Namjae Jeon <linkinjeon@kernel.org>
To: syzbot <syzbot+listb51f932ee38ecac1b05d@syzkaller.appspotmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
sj1557.seo@samsung.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] Monthly exfat report (Nov 2023)
Date: Wed, 29 Nov 2023 23:09:54 +0900 [thread overview]
Message-ID: <CAKYAXd-WLUQcyMAWd_R4PKRcciRh=faNnixv38abWmj7V=To9Q@mail.gmail.com> (raw)
In-Reply-To: <0000000000009401fb060b28a2e1@google.com>
2023-11-28 6:03 GMT+09:00, syzbot
<syzbot+listb51f932ee38ecac1b05d@syzkaller.appspotmail.com>:
> Hello exfat maintainers/developers,
Hi,
>
> This is a 31-day syzbot report for the exfat subsystem.
> All related reports/information can be found at:
> https://syzkaller.appspot.com/upstream/s/exfat
>
> During the period, 1 new issues were detected and 0 were fixed.
> In total, 7 issues are still open and 12 have been fixed so far.
>
> Some of the still happening issues:
>
> Ref Crashes Repro Title
> <1> 225 No INFO: task hung in path_openat (7)
There is no reproducer and I couldn't find where it is connected to exfat.
>
> https://syzkaller.appspot.com/bug?extid=950a0cdaa2fdd14f5bdc
> <2> 150 No INFO: task hung in exfat_sync_fs
There is no reproducer... Let me know how to reproduce it.
This can happen when disk speed is very low and a lot of writes occur.
Is that so?
>
> https://syzkaller.appspot.com/bug?extid=205c2644abdff9d3f9fc
> <3> 119 Yes WARNING in drop_nlink (2)
I'm curious how this issue was classified as an exfat issue.
When looking at the backtrace, this issue appears to be an hfsplus issue.
hfsplus_unlink+0x3fe/0x790 fs/hfsplus/dir.c:381
hfsplus_rename+0xc8/0x1c0 fs/hfsplus/dir.c:547
vfs_rename+0xaba/0xde0 fs/namei.c:4844
>
> https://syzkaller.appspot.com/bug?extid=651ca866e5e2b4b5095b
> <4> 38 Yes INFO: task hung in exfat_write_inode
I could not reproduce this by using C reproducer provided by you.
Can you confirm that this really cannot be reproduced using it?
>
> https://syzkaller.appspot.com/bug?extid=2f73ed585f115e98aee8
> <5> 1 No UBSAN: shift-out-of-bounds in exfat_fill_super (2)
This is false alarm. ->sect_size_bits could not be greater than 12 by
the check below.
/*
* sect_size_bits could be at least 9 and at most 12.
*/
if (p_boot->sect_size_bits < EXFAT_MIN_SECT_SIZE_BITS ||
p_boot->sect_size_bits > EXFAT_MAX_SECT_SIZE_BITS) {
exfat_err(sb, "bogus sector size bits : %u",
p_boot->sect_size_bits);
return -EINVAL;
}
>
> https://syzkaller.appspot.com/bug?extid=d33808a177641a02213e
>
> ---
> This report is generated by a bot. It may contain errors.
> See https://goo.gl/tpsmEJ for more information about syzbot.
> syzbot engineers can be reached at syzkaller@googlegroups.com.
>
> To disable reminders for individual bugs, reply with the following command:
> #syz set <Ref> no-reminders
>
> To change bug's subsystems, reply with:
> #syz set <Ref> subsystems: new-subsystem
>
> You may send multiple commands in a single email message.
>
next prev parent reply other threads:[~2023-11-29 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 21:03 [syzbot] Monthly exfat report (Nov 2023) syzbot
2023-11-29 14:09 ` Namjae Jeon [this message]
2023-11-29 15:48 ` Aleksandr Nogikh
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='CAKYAXd-WLUQcyMAWd_R4PKRcciRh=faNnixv38abWmj7V=To9Q@mail.gmail.com' \
--to=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
--cc=syzbot+listb51f932ee38ecac1b05d@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;
as well as URLs for NNTP newsgroup(s).