From: syzbot <syzbot+7e5cf1d80677ec185e63-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org>
To: akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
brauner-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
konishi.ryusuke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
syzkaller-bugs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org,
willy-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org
Subject: Re: [syzbot] [nilfs?] kernel BUG in folio_end_writeback
Date: Sun, 20 Aug 2023 11:41:23 -0700 [thread overview]
Message-ID: <000000000000d299b406035f1bbd@google.com> (raw)
In-Reply-To: <000000000000dc83d605f0c70a11-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
syzbot suspects this issue was fixed by commit:
commit 92c5d1b860e9581d64baca76779576c0ab0d943d
Author: Ryusuke Konishi <konishi.ryusuke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date: Fri May 26 02:13:32 2023 +0000
nilfs2: reject devices with insufficient block count
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=170c6337a80000
start commit: 929ed21dfdb6 Merge tag '6.4-rc4-smb3-client-fixes' of git:..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=3da6c5d3e0a6c932
dashboard link: https://syzkaller.appspot.com/bug?extid=7e5cf1d80677ec185e63
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16cb3b69280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10f34201280000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: nilfs2: reject devices with insufficient block count
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+7e5cf1d80677ec185e63@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, brauner@kernel.org,
konishi.ryusuke@gmail.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-nilfs@vger.kernel.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk, willy@infradead.org
Subject: Re: [syzbot] [nilfs?] kernel BUG in folio_end_writeback
Date: Sun, 20 Aug 2023 11:41:23 -0700 [thread overview]
Message-ID: <000000000000d299b406035f1bbd@google.com> (raw)
In-Reply-To: <000000000000dc83d605f0c70a11@google.com>
syzbot suspects this issue was fixed by commit:
commit 92c5d1b860e9581d64baca76779576c0ab0d943d
Author: Ryusuke Konishi <konishi.ryusuke@gmail.com>
Date: Fri May 26 02:13:32 2023 +0000
nilfs2: reject devices with insufficient block count
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=170c6337a80000
start commit: 929ed21dfdb6 Merge tag '6.4-rc4-smb3-client-fixes' of git:..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=3da6c5d3e0a6c932
dashboard link: https://syzkaller.appspot.com/bug?extid=7e5cf1d80677ec185e63
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16cb3b69280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10f34201280000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: nilfs2: reject devices with insufficient block count
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-08-20 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 3:42 [syzbot] [nilfs2?] kernel BUG in folio_end_writeback syzbot
2022-12-27 3:42 ` syzbot
[not found] ` <000000000000dc83d605f0c70a11-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2023-08-20 18:41 ` syzbot [this message]
2023-08-20 18:41 ` [syzbot] [nilfs?] " syzbot
2023-08-21 16:47 ` Ryusuke Konishi
2023-08-21 16:47 ` 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=000000000000d299b406035f1bbd@google.com \
--to=syzbot+7e5cf1d80677ec185e63-pl5pbv+gp7p466ipttivnc23woclnbcfal8byrjmmd8@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=brauner-DgEjT+Ai2ygdnm+yROfE0A@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-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=syzkaller-bugs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
--cc=viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org \
--cc=willy-wEGCiKHe2LqWVfeAwA7xHQ@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.