From: Jan Kara <jack@suse.cz>
To: syzbot <syzbot+172bdd582e5d63486948@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?] general protection fault in dtSplitUp
Date: Fri, 12 Jan 2024 10:59:45 +0100 [thread overview]
Message-ID: <20240112095945.oxx42ycamfouw3xs@quack3> (raw)
In-Reply-To: <000000000000ccb6c6060eb767bd@google.com>
On Thu 11-01-24 19:39: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=1268fc69e80000
> start commit: a70385240892 Merge tag 'perf_urgent_for_v6.1_rc2' of git:/..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=ea03ca45176080bc
> dashboard link: https://syzkaller.appspot.com/bug?extid=172bdd582e5d63486948
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15692dba880000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15017b2c880000
>
> If the result looks correct, please mark the issue as fixed by replying with:
Makes sense. When I'm looking at the dashboard I can see there's another
(older) reproducer which is not marked as not reproducing anymore. I
suppose this is because syzbot tests only the latest reproducer? Anyway,
let's close this, if syzbot can find another reproducer for the problem
with writes to mounted devices disabled, it'll surely tell us :)
#syz fix: fs: Block writes to mounted block devices
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2024-01-12 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000ff4a1505e9f961a2@google.com>
2024-01-12 3:39 ` [syzbot] [jfs?] general protection fault in dtSplitUp syzbot
2024-01-12 9:59 ` 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=20240112095945.oxx42ycamfouw3xs@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+172bdd582e5d63486948@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;
as well as URLs for NNTP newsgroup(s).