From: syzbot <syzbot+c300ab283ba3bc072439@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] Re: [syzbot] [ntfs3?] possible deadlock in ni_fiemap
Date: Mon, 18 Nov 2024 03:05:45 -0800 [thread overview]
Message-ID: <673b1f89.050a0220.87769.0033.GAE@google.com> (raw)
In-Reply-To: <0000000000000fc50405eb48a1be@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: Re: [syzbot] [ntfs3?] possible deadlock in ni_fiemap
Author: jack@suse.cz
On Sun 17-11-24 22:58:02, syzbot wrote:
> 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=120c0ac0580000
> start commit: d537ae43f8a1 Merge tag 'gpio-fixes-for-v6.6-rc7' of git://..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=849fe52ba7c6d78a
> dashboard link: https://syzkaller.appspot.com/bug?extid=c300ab283ba3bc072439
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1056076d680000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17093269680000
>
> If the result looks correct, please mark the issue as fixed by replying with:
Makes sense.
#syz fix: fs: Block writes to mounted block devices
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2024-11-18 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 5:47 [syzbot] possible deadlock in ni_fiemap syzbot
2022-11-30 17:25 ` syzbot
2024-07-20 7:43 ` [syzbot] possible fix syzbot
2024-08-23 16:03 ` [syzbot] possible deadlock in ni_fiemap syzbot
2024-11-18 6:58 ` [syzbot] [ntfs3?] " syzbot
2024-11-18 11:05 ` 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=673b1f89.050a0220.87769.0033.GAE@google.com \
--to=syzbot+c300ab283ba3bc072439@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.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.