From: Jan Kara <jack@suse.cz>
To: syzbot <syzbot+7d5fa8eb99155f439221@syzkaller.appspotmail.com>
Cc: adilger.kernel@dilger.ca, apparmor-owner@lists.ubuntu.com,
apparmor@lists.ubuntu.com, axboe@kernel.dk, brauner@kernel.org,
jack@suse.cz, jmorris@namei.org, john.johansen@canonical.com,
john@apparmor.net, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, paul@paul-moore.com,
serge@hallyn.com, syzkaller-bugs@googlegroups.com,
terrelln@fb.com, tytso@mit.edu
Subject: Re: [syzbot] [apparmor?] [ext4?] general protection fault in common_perm_cond
Date: Tue, 20 Feb 2024 11:00:52 +0100 [thread overview]
Message-ID: <20240220100052.gbuy6dopqql7m7yl@quack3> (raw)
In-Reply-To: <000000000000af682a0611c9a06f@google.com>
On Mon 19-02-24 21:39: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=1644f22c180000
> start commit: b6e6cc1f78c7 Merge tag 'x86_urgent_for_6.5_rc2' of git://g..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=6769a69bd0e144b4
> dashboard link: https://syzkaller.appspot.com/bug?extid=7d5fa8eb99155f439221
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=137b16dca80000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14153b7ca80000
>
> 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-02-20 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 1:11 [syzbot] [apparmor?] [ext4?] general protection fault in common_perm_cond syzbot
2024-02-20 5:39 ` syzbot
2024-02-20 10:00 ` 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=20240220100052.gbuy6dopqql7m7yl@quack3 \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=apparmor-owner@lists.ubuntu.com \
--cc=apparmor@lists.ubuntu.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=john@apparmor.net \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=syzbot+7d5fa8eb99155f439221@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=terrelln@fb.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).