From: Aleksandr Nogikh <nogikh@google.com>
To: syzbot <syzbot+278098b0faaf0595072b@syzkaller.appspotmail.com>
Cc: linkinjeon@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, sj1557.seo@samsung.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fat?] possible deadlock in do_user_addr_fault
Date: Tue, 8 Aug 2023 13:00:23 +0200 [thread overview]
Message-ID: <CANp29Y6M-CU+eqUFqN3Rkf2iba7upqsLvnHNNyMmhd4JFdH-8A@mail.gmail.com> (raw)
In-Reply-To: <000000000000a9bf5106026705ec@google.com>
On Tue, Aug 8, 2023 at 12:42 PM syzbot
<syzbot+278098b0faaf0595072b@syzkaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit ff84772fd45d486e4fc78c82e2f70ce5333543e6
> Author: Sungjong Seo <sj1557.seo@samsung.com>
> Date: Fri Jul 14 08:43:54 2023 +0000
>
> exfat: release s_lock before calling dir_emit()
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16623aa9a80000
> start commit: f8dba31b0a82 Merge tag 'asym-keys-fix-for-linus-v6.4-rc5' ..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=3c980bfe8b399968
> dashboard link: https://syzkaller.appspot.com/bug?extid=278098b0faaf0595072b
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=144ccf79280000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=135fab79280000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: exfat: release s_lock before calling dir_emit()
Seems reasonable.
#syz fix: exfat: release s_lock before calling dir_emit()
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/000000000000a9bf5106026705ec%40google.com.
prev parent reply other threads:[~2023-08-08 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 19:53 [syzbot] [fat?] possible deadlock in do_user_addr_fault syzbot
2023-06-06 8:23 ` syzbot
2023-08-08 10:42 ` syzbot
2023-08-08 11:00 ` Aleksandr Nogikh [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=CANp29Y6M-CU+eqUFqN3Rkf2iba7upqsLvnHNNyMmhd4JFdH-8A@mail.gmail.com \
--to=nogikh@google.com \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
--cc=syzbot+278098b0faaf0595072b@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).