From: Jan Kara <jack@suse.cz>
To: syzbot <syzbot+ca4b16c6465dca321d40@syzkaller.appspotmail.com>
Cc: axboe@kernel.dk, brauner@kernel.org, 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: trying to register non-static key in txEnd
Date: Thu, 7 Mar 2024 10:25:17 +0100 [thread overview]
Message-ID: <20240307092517.clgkvqttd4rw6dx5@quack3> (raw)
In-Reply-To: <0000000000006786560612c32ff9@google.com>
On Sun 03-03-24 07:23:03, 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=14e0e374180000
> start commit: c7402612e2e6 Merge tag 'net-6.7-rc6' of git://git.kernel.o..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=b6602324d4e5a4a9
> dashboard link: https://syzkaller.appspot.com/bug?extid=ca4b16c6465dca321d40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16941c8ae80000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13d9c3c1e80000
>
> 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-03-07 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 14:07 syzbot
2024-03-03 15:23 ` syzbot
2024-03-07 9:25 ` Jan Kara [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=20240307092517.clgkvqttd4rw6dx5@quack3 \
--to=jack@suse.cz \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@kernel.org \
--cc=syzbot+ca4b16c6465dca321d40@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®