All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+f59c2feaf7cb5988e877@syzkaller.appspotmail.com>
To: brauner@kernel.org, eadavis@qq.com, linkinjeon@kernel.org,
	 linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	 sandeen@redhat.com, sj1557.seo@samsung.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs] INFO: task hung in do_new_mount (2)
Date: Sat, 17 Aug 2024 02:43:02 -0700	[thread overview]
Message-ID: <000000000000ea066d061fdde62b@google.com> (raw)
In-Reply-To: <00000000000093ea0d06142c361a@google.com>

syzbot suspects this issue was fixed by commit:

commit ffe1b94d7464bef15b6585f9e7f8192cd0668327
Author: Eric Sandeen <sandeen@redhat.com>
Date:   Fri Jun 28 00:31:51 2024 +0000

    exfat: Convert to new uid/gid option parsing helpers

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=17cdae05980000
start commit:   fe46a7dd189e Merge tag 'sound-6.9-rc1' of git://git.kernel..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=4d90a36f0cab495a
dashboard link: https://syzkaller.appspot.com/bug?extid=f59c2feaf7cb5988e877
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1075d2c9180000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=161012a5180000

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

#syz fix: exfat: Convert to new uid/gid option parsing helpers

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

      parent reply	other threads:[~2024-08-17  9:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21 14:06 [syzbot] [exfat?] INFO: task hung in do_new_mount (2) syzbot
2024-03-24  6:33 ` Edward Adam Davis
2024-03-24  7:02   ` syzbot
2024-06-04 14:57 ` Chao Yu
2024-08-17  9:43 ` 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=000000000000ea066d061fdde62b@google.com \
    --to=syzbot+f59c2feaf7cb5988e877@syzkaller.appspotmail.com \
    --cc=brauner@kernel.org \
    --cc=eadavis@qq.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --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.