From: syzbot <syzbot+74db8b3087f293d3a13a-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org>
To: akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
konishi.ryusuke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
syzkaller-bugs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: [syzbot] [nilfs?] KASAN: slab-use-after-free Read in nilfs_load_inode_block (2)
Date: Thu, 27 Jul 2023 14:56:25 -0700 [thread overview]
Message-ID: <00000000000019b5b106017f096a@google.com> (raw)
In-Reply-To: <000000000000b4e906060113fd63-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
syzbot has bisected this issue to:
commit 28a65b49eb53e172d23567005465019658bfdb4d
Author: Ryusuke Konishi <konishi.ryusuke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date: Thu Apr 27 01:15:26 2023 +0000
nilfs2: do not write dirty data after degenerating to read-only
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=177150e5a80000
start commit: 5f0bc0b042fc mm: suppress mm fault logging if fatal signal..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=14f150e5a80000
console output: https://syzkaller.appspot.com/x/log.txt?x=10f150e5a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=5d10d93e1ae1f229
dashboard link: https://syzkaller.appspot.com/bug?extid=74db8b3087f293d3a13a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15176d81a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=132d93d9a80000
Reported-by: syzbot+74db8b3087f293d3a13a-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org
Fixes: 28a65b49eb53 ("nilfs2: do not write dirty data after degenerating to read-only")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+74db8b3087f293d3a13a@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, konishi.ryusuke@gmail.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nilfs@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [nilfs?] KASAN: slab-use-after-free Read in nilfs_load_inode_block (2)
Date: Thu, 27 Jul 2023 14:56:25 -0700 [thread overview]
Message-ID: <00000000000019b5b106017f096a@google.com> (raw)
In-Reply-To: <000000000000b4e906060113fd63@google.com>
syzbot has bisected this issue to:
commit 28a65b49eb53e172d23567005465019658bfdb4d
Author: Ryusuke Konishi <konishi.ryusuke@gmail.com>
Date: Thu Apr 27 01:15:26 2023 +0000
nilfs2: do not write dirty data after degenerating to read-only
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=177150e5a80000
start commit: 5f0bc0b042fc mm: suppress mm fault logging if fatal signal..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=14f150e5a80000
console output: https://syzkaller.appspot.com/x/log.txt?x=10f150e5a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=5d10d93e1ae1f229
dashboard link: https://syzkaller.appspot.com/bug?extid=74db8b3087f293d3a13a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15176d81a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=132d93d9a80000
Reported-by: syzbot+74db8b3087f293d3a13a@syzkaller.appspotmail.com
Fixes: 28a65b49eb53 ("nilfs2: do not write dirty data after degenerating to read-only")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-07-27 21:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 14:13 [syzbot] [nilfs?] KASAN: slab-use-after-free Read in nilfs_load_inode_block (2) syzbot
[not found] ` <000000000000b4e906060113fd63-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2023-07-27 7:52 ` syzbot
2023-07-27 7:52 ` syzbot
2023-07-27 21:56 ` syzbot [this message]
2023-07-27 21:56 ` syzbot
2023-07-28 19:13 ` [PATCH] nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput Ryusuke Konishi
2023-07-28 19:13 ` Ryusuke Konishi
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=00000000000019b5b106017f096a@google.com \
--to=syzbot+74db8b3087f293d3a13a-pl5pbv+gp7p466ipttivnc23woclnbcfal8byrjmmd8@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=konishi.ryusuke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=syzkaller-bugs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.