From: Ryusuke Konishi <konishi.ryusuke@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: syzbot <syzbot+4936b06b07f365af31cc@syzkaller.appspotmail.com>,
axboe@kernel.dk, brauner@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nilfs@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [nilfs?] KASAN: use-after-free Read in nilfs_set_link
Date: Mon, 19 Feb 2024 21:13:09 +0900 [thread overview]
Message-ID: <CAKFNMonaAqehuHVW1beMNfgYm1Y8_hcjAZGAC1F5zs-3zcPQjQ@mail.gmail.com> (raw)
In-Reply-To: <20240219114719.pyntouzverbsk4da@quack3>
On Mon, Feb 19, 2024 at 8:47 PM Jan Kara wrote:
>
> On Sat 17-02-24 20:42: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=10639b34180000
> > start commit: 52b1853b080a Merge tag 'i2c-for-6.7-final' of git://git.ke..
> > git tree: upstream
> > kernel config: https://syzkaller.appspot.com/x/.config?x=655f8abe9fe69b3b
> > dashboard link: https://syzkaller.appspot.com/bug?extid=4936b06b07f365af31cc
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11d62025e80000
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13c38055e80000
> >
> > If the result looks correct, please mark the issue as fixed by replying with:
> >
> > #syz fix: fs: Block writes to mounted block devices
>
> The reproducers don't seem to be doing anything suspicious so I'm not sure
> why the commit makes them not work anymore. There are no working
> reproducers for this bug though so I'll leave it upto the nilfs maintainer
> to decide what to do.
>
> Honza
>
> --
> Jan Kara <jack@suse.com>
> SUSE Labs, CR
Thank you for your comment.
This is one of the issues that I could not reproduce and could not
proceed with the analysis, but since it may be caused by an abnormal
state of the directory file (even if it was overwritten), I would like
to leave it as a subject of investigation.
Thanks,
Ryusuke Konishi
prev parent reply other threads:[~2024-02-19 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 20:06 [syzbot] [nilfs?] KASAN: use-after-free Read in nilfs_set_link syzbot
2024-02-18 4:42 ` syzbot
2024-02-19 11:47 ` Jan Kara
2024-02-19 12:13 ` Ryusuke Konishi [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=CAKFNMonaAqehuHVW1beMNfgYm1Y8_hcjAZGAC1F5zs-3zcPQjQ@mail.gmail.com \
--to=konishi.ryusuke@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=syzbot+4936b06b07f365af31cc@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 read-only IMAP folder(s) and NNTP newsgroup(s).