From: Jan Kara <jack@suse.cz>
To: syzbot <syzbot+ba698041fcdf4d0214bb@syzkaller.appspotmail.com>
Cc: almaz.alexandrovich@paragon-software.com, axboe@kernel.dk,
brauner@kernel.org, jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk,
yuran.pereira@hotmail.com
Subject: Re: [syzbot] [ntfs3?] kernel panic: stack is corrupted in run_unpack_ex
Date: Wed, 21 Feb 2024 11:23:40 +0100 [thread overview]
Message-ID: <20240221102340.auf7ltb7yikmysf4@quack3> (raw)
In-Reply-To: <0000000000007a3b2a0611d18c03@google.com>
On Tue 20-02-24 07:06: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=149d61e8180000
> start commit: 41c03ba9beea Merge tag 'for_linus' of git://git.kernel.org..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=8cdb1e7bec4b955a
> dashboard link: https://syzkaller.appspot.com/bug?extid=ba698041fcdf4d0214bb
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11e43f56480000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13fbabea480000
>
> 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-21 10:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 8:04 [syzbot] [ntfs3?] kernel panic: stack is corrupted in run_unpack_ex syzbot
2024-02-20 15:06 ` syzbot
2024-02-21 10:23 ` 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=20240221102340.auf7ltb7yikmysf4@quack3 \
--to=jack@suse.cz \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=syzbot+ba698041fcdf4d0214bb@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yuran.pereira@hotmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).