From: Ryusuke Konishi <konishi.ryusuke@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-nilfs <linux-nilfs@vger.kernel.org>,
syzbot <syzbot+9bff4c7b992038a7409f@syzkaller.appspotmail.com>,
syzkaller-bugs@googlegroups.com,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] nilfs2: fix potential issues with empty b-tree nodes
Date: Wed, 4 Sep 2024 17:13:06 +0900 [thread overview]
Message-ID: <20240904081401.16682-1-konishi.ryusuke@gmail.com> (raw)
In-Reply-To: <000000000000b4cf9a062114d132@google.com>
Hi Andrew,
please add this series to the queue for the next cycle.
This addresses three potential issues with empty b-tree nodes that can
occur with corrupted filesystem images, including one recently
discovered by syzbot.
Thanks,
Ryusuke Konishi
Ryusuke Konishi (3):
nilfs2: fix potential null-ptr-deref in nilfs_btree_insert()
nilfs2: determine empty node blocks as corrupted
nilfs2: fix potential oob read in nilfs_btree_check_delete()
fs/nilfs2/btree.c | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
--
2.43.0
next prev parent reply other threads:[~2024-09-04 8:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-01 20:39 [syzbot] [nilfs?] general protection fault in nilfs_btree_insert (2) syzbot
2024-09-02 8:41 ` Lizhi Xu
2024-09-02 10:08 ` syzbot
2024-09-02 19:40 ` Ryusuke Konishi
2024-09-04 8:13 ` Ryusuke Konishi [this message]
2024-09-04 8:13 ` [PATCH 1/3] nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() Ryusuke Konishi
2024-09-04 8:13 ` [PATCH 2/3] nilfs2: determine empty node blocks as corrupted Ryusuke Konishi
2024-09-04 8:13 ` [PATCH 3/3] nilfs2: fix potential oob read in nilfs_btree_check_delete() 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=20240904081401.16682-1-konishi.ryusuke@gmail.com \
--to=konishi.ryusuke@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=syzbot+9bff4c7b992038a7409f@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 NNTP newsgroup(s).