From: Ryusuke Konishi <konishi.ryusuke@gmail.com> To: Andrew Morton <akpm@linux-foundation.org> Cc: linux-nilfs <linux-nilfs@vger.kernel.org>, syzbot <syzbot+e91619dd4c11c4960706@syzkaller.appspotmail.com>, syzkaller-bugs@googlegroups.com, LKML <linux-kernel@vger.kernel.org> Subject: [PATCH 0/2] nilfs2: fix UBSAN shift-out-of-bounds warnings on mount time Date: Thu, 27 Oct 2022 13:43:04 +0900 [thread overview] Message-ID: <20221027044306.42774-1-konishi.ryusuke@gmail.com> (raw) Hi Andrew, please apply the following bug fixes to -mm tree: Ryusuke Konishi (2): nilfs2: fix shift-out-of-bounds/overflow in nilfs_sb2_bad_offset() nilfs2: fix shift-out-of-bounds due to too large exponent of block size The first patch fixes a reported bug by syzbot, and the second one fixes the remaining bug of the same kind. Although they are triggered by the same super block data anomaly, I divided it into the above two because the details of the issues and how to fix it are different. Both are required to eliminate the shift-out-of-bounds issues on mount time. Thanks, Ryusuke Konishi fs/nilfs2/the_nilfs.c | 73 ++++++++++++++++++++++++++++++++++++++----- 1 file changed, 65 insertions(+), 8 deletions(-) -- 2.34.1
WARNING: multiple messages have this Message-ID (diff)
From: Ryusuke Konishi <konishi.ryusuke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> To: Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org> Cc: linux-nilfs <linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, syzbot <syzbot+e91619dd4c11c4960706-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org>, syzkaller-bugs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org, LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> Subject: [PATCH 0/2] nilfs2: fix UBSAN shift-out-of-bounds warnings on mount time Date: Thu, 27 Oct 2022 13:43:04 +0900 [thread overview] Message-ID: <20221027044306.42774-1-konishi.ryusuke@gmail.com> (raw) Hi Andrew, please apply the following bug fixes to -mm tree: Ryusuke Konishi (2): nilfs2: fix shift-out-of-bounds/overflow in nilfs_sb2_bad_offset() nilfs2: fix shift-out-of-bounds due to too large exponent of block size The first patch fixes a reported bug by syzbot, and the second one fixes the remaining bug of the same kind. Although they are triggered by the same super block data anomaly, I divided it into the above two because the details of the issues and how to fix it are different. Both are required to eliminate the shift-out-of-bounds issues on mount time. Thanks, Ryusuke Konishi fs/nilfs2/the_nilfs.c | 73 ++++++++++++++++++++++++++++++++++++++----- 1 file changed, 65 insertions(+), 8 deletions(-) -- 2.34.1
next reply other threads:[~2022-10-27 4:43 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-27 4:43 Ryusuke Konishi [this message] 2022-10-27 4:43 ` [PATCH 0/2] nilfs2: fix UBSAN shift-out-of-bounds warnings on mount time Ryusuke Konishi 2022-10-27 4:43 ` [PATCH 1/2] nilfs2: fix shift-out-of-bounds/overflow in nilfs_sb2_bad_offset() Ryusuke Konishi 2022-10-27 4:43 ` Ryusuke Konishi 2022-10-27 4:43 ` [PATCH 2/2] nilfs2: fix shift-out-of-bounds due to too large exponent of block size Ryusuke Konishi 2022-10-27 4:43 ` 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=20221027044306.42774-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+e91619dd4c11c4960706@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: linkBe 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.