All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+352d78bd60c8e9d6ecdc@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, axboe@kernel.dk, brauner@kernel.org,
	 elic@nvidia.com, jack@suse.cz, jasowang@redhat.com,
	 linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	 linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
	mst@redhat.com,  nathan@kernel.org, ndesaulniers@google.com,
	parav@nvidia.com,  syzkaller-bugs@googlegroups.com,
	trix@redhat.com, tytso@mit.edu
Subject: Re: [syzbot] [ext4?] possible deadlock in ext4_xattr_inode_iget (2)
Date: Fri, 08 Mar 2024 06:06:04 -0800	[thread overview]
Message-ID: <00000000000044b90e061326b102@google.com> (raw)
In-Reply-To: <0000000000005b767405ffd4e4ec@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=14f08e0a180000
start commit:   610a9b8f49fb Linux 6.7-rc8
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=56c2c781bb4ee18
dashboard link: https://syzkaller.appspot.com/bug?extid=352d78bd60c8e9d6ecdc
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=15a4d65ee80000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1715ad7ee80000

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-03-08 14:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06 17:31 [syzbot] [ext4?] possible deadlock in ext4_xattr_inode_iget (2) syzbot
2024-03-08 14:06 ` syzbot [this message]
2024-03-11 17:54   ` Jan Kara

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=00000000000044b90e061326b102@google.com \
    --to=syzbot+352d78bd60c8e9d6ecdc@syzkaller.appspotmail.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=elic@nvidia.com \
    --cc=jack@suse.cz \
    --cc=jasowang@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mst@redhat.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=parav@nvidia.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=trix@redhat.com \
    --cc=tytso@mit.edu \
    /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.