All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+fb337a5ea8454f5f1e3f@syzkaller.appspotmail.com>
To: axboe@kernel.dk, brauner@kernel.org, hdanton@sina.com,
	jack@suse.cz,  jfs-discussion@lists.sourceforge.net,
	linux-fsdevel@vger.kernel.org,  linux-kernel@vger.kernel.org,
	shaggy@kernel.org,  syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [jfs?] INFO: task hung in path_mount (2)
Date: Thu, 25 Jan 2024 03:59:03 -0800	[thread overview]
Message-ID: <000000000000e5e71a060fc3e747@google.com> (raw)
In-Reply-To: <00000000000083513f060340d472@google.com>

syzbot suspects this issue was fixed by commit:

commit 6f861765464f43a71462d52026fbddfc858239a5
Author: Jan Kara <jack@suse.cz>
Date:   Wed Nov 1 17:43:10 2023 +0000

    fs: Block writes to mounted block devices

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=13175a53e80000
start commit:   2ccdd1b13c59 Linux 6.5-rc6
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=9c37cc0e4fcc5f8d
dashboard link: https://syzkaller.appspot.com/bug?extid=fb337a5ea8454f5f1e3f
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17ba5d53a80000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=14265373a80000

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

#syz fix: fs: Block writes to mounted block devices

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

  reply	other threads:[~2024-01-25 11:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-19  6:33 [syzbot] [jfs?] INFO: task hung in path_mount (2) syzbot
2024-01-25 11:59 ` syzbot [this message]
2024-01-25 16:08   ` Christian Brauner
2024-01-25 16:11     ` Jens Axboe
2024-01-25 16:47       ` Christian Brauner
2024-01-25 16:51         ` Jens Axboe
2024-01-25 16:55           ` Christian Brauner
2024-01-25 18:24         ` Aleksandr Nogikh
2024-01-26  9:28           ` Christian Brauner
     [not found] <20230820014135.2475-1-hdanton@sina.com>
2023-08-20  3:15 ` syzbot

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=000000000000e5e71a060fc3e747@google.com \
    --to=syzbot+fb337a5ea8454f5f1e3f@syzkaller.appspotmail.com \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=hdanton@sina.com \
    --cc=jack@suse.cz \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaggy@kernel.org \
    --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.