From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Allison Henderson <achender@linux.vnet.ibm.com>
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>,
kernel@collabora.com, stable@vger.kernel.org,
syzbot+6e5f2db05775244c73b7@syzkaller.appspotmail.com,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] ext4: don't remove already removed extent
Date: Mon, 11 Sep 2023 14:57:02 +0500 [thread overview]
Message-ID: <4af6a370-6d31-4413-b78e-e693be5f01a9@collabora.com> (raw)
In-Reply-To: <20230911094038.3602508-1-usama.anjum@collabora.com>
Apologies for sending multiple copies of same email. There was some issue
on my side.
On 9/11/23 2:40 PM, Muhammad Usama Anjum wrote:
> Syzbot has hit the following bug on current and all older kernels:
> BUG: KASAN: out-of-bounds in ext4_ext_rm_leaf fs/ext4/extents.c:2736 [inline]
> BUG: KASAN: out-of-bounds in ext4_ext_remove_space+0x2482/0x4d90 fs/ext4/extents.c:2958
> Read of size 18446744073709551508 at addr ffff888073aea078 by task syz-executor420/6443
>
> On investigation, I've found that eh->eh_entries is zero, ex is
> referring to last entry and EXT_LAST_EXTENT(eh) is referring to first.
> Hence EXT_LAST_EXTENT(eh) - ex becomes negative and causes the wrong
> buffer read.
>
> element: FFFF8882F8F0D06C <----- ex
> element: FFFF8882F8F0D060
> element: FFFF8882F8F0D054
> element: FFFF8882F8F0D048
> element: FFFF8882F8F0D03C
> element: FFFF8882F8F0D030
> element: FFFF8882F8F0D024
> element: FFFF8882F8F0D018
> element: FFFF8882F8F0D00C <------ EXT_FIRST_EXTENT(eh)
> header: FFFF8882F8F0D000 <------ EXT_LAST_EXTENT(eh) and eh
>
> Cc: stable@vger.kernel.org
> Reported-by: syzbot+6e5f2db05775244c73b7@syzkaller.appspotmail.com
> Closes: https://groups.google.com/g/syzkaller-bugs/c/G6zS-LKgDW0/m/63MgF6V7BAAJ
> Fixes: d583fb87a3ff ("ext4: punch out extents")
> Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
> ---
> This patch is only fixing the local issue. There may be bigger bug. Why
> is ex set to last entry if the eh->eh_entries is 0. If any ext4
> developer want to look at the bug, please don't hesitate.
> ---
> fs/ext4/extents.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
> index e4115d338f101..7b7779b4cb87f 100644
> --- a/fs/ext4/extents.c
> +++ b/fs/ext4/extents.c
> @@ -2726,7 +2726,7 @@ ext4_ext_rm_leaf(handle_t *handle, struct inode *inode,
> * If the extent was completely released,
> * we need to remove it from the leaf
> */
> - if (num == 0) {
> + if (num == 0 && eh->eh_entries) {
> if (end != EXT_MAX_BLOCKS - 1) {
> /*
> * For hole punching, we need to scoot all the
--
BR,
Muhammad Usama Anjum
next prev parent reply other threads:[~2023-09-11 21:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 9:40 [RFC] ext4: don't remove already removed extent Muhammad Usama Anjum
2023-09-11 9:57 ` Muhammad Usama Anjum [this message]
2023-09-20 0:41 ` Eric Whitney
2023-10-06 10:47 ` Muhammad Usama Anjum
2023-10-08 21:10 ` Eric Whitney
-- strict thread matches above, loose matches on Subject: below --
2023-09-11 9:24 Muhammad Usama Anjum
2023-09-11 9:13 [RFC] ext4: don't' " Muhammad Usama Anjum
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=4af6a370-6d31-4413-b78e-e693be5f01a9@collabora.com \
--to=usama.anjum@collabora.com \
--cc=achender@linux.vnet.ibm.com \
--cc=adilger.kernel@dilger.ca \
--cc=kernel@collabora.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+6e5f2db05775244c73b7@syzkaller.appspotmail.com \
--cc=tytso@mit.edu \
/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