All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+247e66a2c3ea756332c7@syzkaller.appspotmail.com>
To: hdanton@sina.com, linkinjeon@kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	sj1557.seo@samsung.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [exfat?] possible deadlock in exfat_get_block
Date: Sat, 07 Oct 2023 11:47:29 -0700	[thread overview]
Message-ID: <000000000000ff17f2060724c971@google.com> (raw)
In-Reply-To: <00000000000073500205eac39838@google.com>

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=12f6bef1680000
start commit:   5d0c230f1de8 Linux 6.5-rc4
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=27a4e50cc5856a15
dashboard link: https://syzkaller.appspot.com/bug?extid=247e66a2c3ea756332c7
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12532d91a80000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=105aae2ea80000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: exfat: release s_lock before calling dir_emit()

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2023-10-07 18:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 15:04 [syzbot] possible deadlock in exfat_get_block syzbot
2022-11-15 10:47 ` syzbot
2023-10-07 18:47 ` syzbot [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=000000000000ff17f2060724c971@google.com \
    --to=syzbot+247e66a2c3ea756332c7@syzkaller.appspotmail.com \
    --cc=hdanton@sina.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sj1557.seo@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.