linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namjae Jeon <linkinjeon@kernel.org>
To: syzbot <syzbot+list96b6ab127c02d379290b@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 fat report (Jul 2023)
Date: Fri, 14 Jul 2023 22:38:25 +0900	[thread overview]
Message-ID: <CAKYAXd9Wv5Swj4fouCLYbdyjWYhT39C3TiHgm-fRiKS_2=zsTA@mail.gmail.com> (raw)
In-Reply-To: <00000000000075fd0505ff917517@google.com>

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 :)
>
> 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
>
> https://syzkaller.appspot.com/bug?extid=fb8d39ebb665f80c2ec1
> <7> 1       Yes   BUG: corrupted list in __mark_inode_dirty
>
> 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

Numbers <6>, <7> are not exfat issues. Can you remove them in your list?

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.
>

  reply	other threads:[~2023-07-14 13:38 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 [this message]
2023-07-14 17:46   ` Aleksandr Nogikh
2023-07-14 23:29     ` Namjae Jeon

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='CAKYAXd9Wv5Swj4fouCLYbdyjWYhT39C3TiHgm-fRiKS_2=zsTA@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+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).