public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+e245f0516ee625aaa412@syzkaller.appspotmail.com>
To: axboe@kernel.dk, brauner@kernel.org, david@fromorbit.com,
	 djwong@kernel.org, jack@suse.cz, linux-fsdevel@vger.kernel.org,
	 linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
	llvm@lists.linux.dev,  mjguzik@gmail.com, nathan@kernel.org,
	ndesaulniers@google.com,  nogikh@google.com,
	syzkaller-bugs@googlegroups.com, trix@redhat.com,  tytso@mit.edu,
	viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [fs] INFO: task hung in __fdget_pos (4)
Date: Thu, 31 Oct 2024 06:38:02 -0700	[thread overview]
Message-ID: <6723883a.050a0220.35b515.015f.GAE@google.com> (raw)
In-Reply-To: <000000000000e6432a06046c96a5@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=11fc5540580000
start commit:   3b47bc037bd4 Merge tag 'pinctrl-v6.7-2' of git://git.kerne..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=c2c74446ab4f0028
dashboard link: https://syzkaller.appspot.com/bug?extid=e245f0516ee625aaa412
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11026e54e80000

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

      parent reply	other threads:[~2024-10-31 13:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-03  4:11 [syzbot] [xfs?] INFO: task hung in __fdget_pos (4) syzbot
2023-09-03  5:25 ` Dave Chinner
2023-09-03  8:33   ` Mateusz Guzik
2023-09-03 18:01     ` Al Viro
2023-09-03 18:57       ` Mateusz Guzik
2023-09-03 19:51         ` Al Viro
2023-09-03 20:04           ` Mateusz Guzik
2023-09-06 17:53             ` Aleksandr Nogikh
2023-09-03 22:27     ` Dave Chinner
2023-09-03 22:47       ` Mateusz Guzik
2023-09-03 23:09         ` Dave Chinner
2023-09-04  8:11           ` Christian Brauner
2023-09-04  8:23             ` Christian Brauner
2023-09-04  8:55               ` Dave Chinner
2023-09-03 23:13       ` Al Viro
2023-09-04  1:45         ` Dave Chinner
2023-09-04  3:02           ` Al Viro
2023-09-04  3:26           ` Theodore Ts'o
2023-09-04  6:09             ` Mateusz Guzik
2023-11-30 16:58 ` [syzbot] [fs] " syzbot
2024-09-21  5:58 ` syzbot
2024-10-31 13:38 ` 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=6723883a.050a0220.35b515.015f.GAE@google.com \
    --to=syzbot+e245f0516ee625aaa412@syzkaller.appspotmail.com \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mjguzik@gmail.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=nogikh@google.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=trix@redhat.com \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    /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