From: syzbot <syzbot+28aaddd5a3221d7fd709@syzkaller.appspotmail.com>
To: axboe@kernel.dk, brauner@kernel.org, jack@suse.cz,
jmorris@namei.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, paul@paul-moore.com,
penguin-kernel@I-love.SAKURA.ne.jp,
penguin-kernel@i-love.sakura.ne.jp, serge@hallyn.com,
syzkaller-bugs@googlegroups.com, takedakn@nttdata.co.jp,
tomoyo-dev-en-owner@lists.osdn.me, tomoyo-dev-en@lists.osdn.me
Subject: Re: [syzbot] [hfs] general protection fault in tomoyo_check_acl (3)
Date: Wed, 10 Jan 2024 22:44:04 -0800 [thread overview]
Message-ID: <0000000000009e1b00060ea5df51@google.com> (raw)
In-Reply-To: <000000000000fcfb4a05ffe48213@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=15135c0be80000
start commit: a901a3568fd2 Merge tag 'iomap-6.5-merge-1' of git://git.ke..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=7406f415f386e786
dashboard link: https://syzkaller.appspot.com/bug?extid=28aaddd5a3221d7fd709
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17b5bb80a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10193ee7280000
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
next prev parent reply other threads:[~2024-01-11 6:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 12:09 [syzbot] [tomoyo?] [hfs?] general protection fault in tomoyo_check_acl (3) syzbot
2023-07-08 11:29 ` Tetsuo Handa
2023-07-08 12:45 ` Tetsuo Handa
2024-01-11 6:44 ` syzbot [this message]
2024-01-11 9:21 ` [syzbot] [hfs] " Jan Kara
2024-03-10 0:52 ` Tetsuo Handa
2024-03-14 15:54 ` Jan Kara
2024-03-14 16:21 ` Aleksandr Nogikh
2024-03-14 17:27 ` Jan Kara
2024-03-15 13:29 ` Christian Brauner
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=0000000000009e1b00060ea5df51@google.com \
--to=syzbot+28aaddd5a3221d7fd709@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=jmorris@namei.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=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=serge@hallyn.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=takedakn@nttdata.co.jp \
--cc=tomoyo-dev-en-owner@lists.osdn.me \
--cc=tomoyo-dev-en@lists.osdn.me \
/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).