From: Namjae Jeon <linkinjeon@kernel.org>
To: Aleksandr Nogikh <nogikh@google.com>
Cc: syzbot
<syzbot+list96b6ab127c02d379290b@syzkaller.appspotmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
sj1557.seo@samsung.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] Monthly fat report (Jul 2023)
Date: Sat, 15 Jul 2023 08:29:47 +0900 [thread overview]
Message-ID: <CAKYAXd-A9D3EtU=0+Qt5ktQH_KVdrvLFiSWB73964fmhkjVrRg@mail.gmail.com> (raw)
In-Reply-To: <CANp29Y7ynmqhmRQ0hABs=uVHQY1sN+Ldw3V93UGSxh+SqfYC=Q@mail.gmail.com>
2023-07-15 2:46 GMT+09:00, Aleksandr Nogikh <nogikh@google.com>:
> On Fri, Jul 14, 2023 at 3:45 PM Namjae Jeon <linkinjeon@kernel.org> wrote:
>>
>> 2023-07-03 18:04 GMT+09:00, syzbot
>> <syzbot+list96b6ab127c02d379290b@syzkaller.appspotmail.com>:
>> > Hello fat maintainers/developers,
>> Hi Syzbot,
>>
>> It's not fat, it's exfat :)
>
> I'll look into renaming it on syzbot :)
>
>> >
>> > This is a 31-day syzbot report for the fat subsystem.
>> > All related reports/information can be found at:
>> > https://syzkaller.appspot.com/upstream/s/fat
>> >
>> > During the period, 3 new issues were detected and 0 were fixed.
>> > In total, 11 issues are still open and 20 have been fixed so far.
>> >
>> > Some of the still happening issues:
>> >
>> > Ref Crashes Repro Title
>> > <1> 347 Yes possible deadlock in filemap_fault
>> >
>> > https://syzkaller.appspot.com/bug?extid=7736960b837908f3a81d
>> > <2> 257 Yes possible deadlock in exfat_get_block
>> >
>> > https://syzkaller.appspot.com/bug?extid=247e66a2c3ea756332c7
>> > <3> 181 Yes possible deadlock in exfat_iterate
>> >
>> > https://syzkaller.appspot.com/bug?extid=38655f1298fefc58a904
>> > <4> 100 Yes possible deadlock in exc_page_fault
>> >
>> > https://syzkaller.appspot.com/bug?extid=6d274a5dc4fa0974d4ad
>> > <5> 39 Yes possible deadlock in do_user_addr_fault
>> >
>> > https://syzkaller.appspot.com/bug?extid=278098b0faaf0595072b
>> > <6> 2 Yes KASAN: slab-use-after-free Write in
>> > collect_expired_timers
>
> #syz set <6> subsystems: reiserfs
>
>> >
>> > https://syzkaller.appspot.com/bug?extid=fb8d39ebb665f80c2ec1
>> > <7> 1 Yes BUG: corrupted list in __mark_inode_dirty
>
> #syz set <7> subsystems: reiserfs
>
>> >
>> > https://syzkaller.appspot.com/bug?extid=4a16683f5520de8e47c4
>> >
>>
>> Can you check if deadlock problem(<1>, <2>, <3>, <4>, <5>, <6>) are
>> fixed with the following patch ?
>> https://lore.kernel.org/lkml/20230714084354.1959951-1-sj1557.seo@samsung.com/T/#u
>
> We currently unfortunately don't support bulk testing, I've sent a few
> requests manually (<1>, <3>, <4>):
> https://groups.google.com/g/syzkaller-bugs/c/ynCUkcnqEiQ/m/qsVWSdWOBAAJ
> https://groups.google.com/g/syzkaller-bugs/c/jKpqY82OuZk
> https://groups.google.com/g/syzkaller-bugs/c/7CO-77jYTAQ/m/lBmXby-OBAAJ
I understood that the problem are fixed with this patch. We will apply
it with syzbot's tested-by tag.
Thanks for your help!
>
>>
>> Numbers <6>, <7> are not exfat issues. Can you remove them in your list?
>
> Thanks for triaging! I've updated their subsystems to reiserfs (see
> commands above).
>
>>
>> Thanks.
>> > ---
>> > 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.
>> >
>>
>> --
>
prev parent reply other threads:[~2023-07-14 23:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 9:04 [syzbot] Monthly fat report (Jul 2023) syzbot
2023-07-14 13:38 ` Namjae Jeon
2023-07-14 17:46 ` Aleksandr Nogikh
2023-07-14 23:29 ` Namjae Jeon [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='CAKYAXd-A9D3EtU=0+Qt5ktQH_KVdrvLFiSWB73964fmhkjVrRg@mail.gmail.com' \
--to=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nogikh@google.com \
--cc=sj1557.seo@samsung.com \
--cc=syzbot+list96b6ab127c02d379290b@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).