From: Jan Kara <jack@suse.cz>
To: libaokun@huaweicloud.com
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu,
adilger.kernel@dilger.ca, jack@suse.cz, ritesh.list@gmail.com,
linux-kernel@vger.kernel.org, yi.zhang@huawei.com,
yangerkun@huawei.com, Baokun Li <libaokun1@huawei.com>,
syzbot+ae688d469e36fb5138d0@syzkaller.appspotmail.com,
stable@kernel.org
Subject: Re: [PATCH 2/2] ext4: make sure the first directory block is not a hole
Date: Wed, 3 Jul 2024 11:36:29 +0200 [thread overview]
Message-ID: <20240703093629.bm32twullwiqmkmp@quack3> (raw)
In-Reply-To: <20240702132349.2600605-3-libaokun@huaweicloud.com>
On Tue 02-07-24 21:23:49, libaokun@huaweicloud.com wrote:
> From: Baokun Li <libaokun1@huawei.com>
>
> The syzbot constructs a directory that has no dirblock but is non-inline,
> i.e. the first directory block is a hole. And no errors are reported when
> creating files in this directory in the following flow.
>
> ext4_mknod
> ...
> ext4_add_entry
> // Read block 0
> ext4_read_dirblock(dir, block, DIRENT)
> bh = ext4_bread(NULL, inode, block, 0)
> if (!bh && (type == INDEX || type == DIRENT_HTREE))
> // The first directory block is a hole
> // But type == DIRENT, so no error is reported.
>
> After that, we get a directory block without '.' and '..' but with a valid
> dentry. This may cause some code that relies on dot or dotdot (such as
> make_indexed_dir()) to crash.
>
> Therefore when ext4_read_dirblock() finds that the first directory block
> is a hole report that the filesystem is corrupted and return an error to
> avoid loading corrupted data from disk causing something bad.
>
> Reported-by: syzbot+ae688d469e36fb5138d0@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=ae688d469e36fb5138d0
> Fixes: 4e19d6b65fb4 ("ext4: allow directory holes")
> Cc: stable@kernel.org
> Signed-off-by: Baokun Li <libaokun1@huawei.com>
Looks good to me. Feel free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> fs/ext4/namei.c | 17 ++++++-----------
> 1 file changed, 6 insertions(+), 11 deletions(-)
>
> diff --git a/fs/ext4/namei.c b/fs/ext4/namei.c
> index 35881e3dd880..6a95713f9193 100644
> --- a/fs/ext4/namei.c
> +++ b/fs/ext4/namei.c
> @@ -151,10 +151,11 @@ static struct buffer_head *__ext4_read_dirblock(struct inode *inode,
>
> return bh;
> }
> - if (!bh && (type == INDEX || type == DIRENT_HTREE)) {
> + /* The first directory block must not be a hole. */
> + if (!bh && (type == INDEX || type == DIRENT_HTREE || block == 0)) {
> ext4_error_inode(inode, func, line, block,
> - "Directory hole found for htree %s block",
> - (type == INDEX) ? "index" : "leaf");
> + "Directory hole found for htree %s block %u",
> + (type == INDEX) ? "index" : "leaf", block);
> return ERR_PTR(-EFSCORRUPTED);
> }
> if (!bh)
> @@ -3084,10 +3085,7 @@ bool ext4_empty_dir(struct inode *inode)
> EXT4_ERROR_INODE(inode, "invalid size");
> return false;
> }
> - /* The first directory block must not be a hole,
> - * so treat it as DIRENT_HTREE
> - */
> - bh = ext4_read_dirblock(inode, 0, DIRENT_HTREE);
> + bh = ext4_read_dirblock(inode, 0, EITHER);
> if (IS_ERR(bh))
> return false;
>
> @@ -3529,10 +3527,7 @@ static struct buffer_head *ext4_get_first_dir_block(handle_t *handle,
> struct ext4_dir_entry_2 *de;
> unsigned int offset;
>
> - /* The first directory block must not be a hole, so
> - * treat it as DIRENT_HTREE
> - */
> - bh = ext4_read_dirblock(inode, 0, DIRENT_HTREE);
> + bh = ext4_read_dirblock(inode, 0, EITHER);
> if (IS_ERR(bh)) {
> *retval = PTR_ERR(bh);
> return NULL;
> --
> 2.39.2
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2024-07-03 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 13:23 [PATCH 0/2] ext4: fix unable to handle kernel paging request in do_split() libaokun
2024-07-02 13:23 ` [PATCH 1/2] ext4: check dot and dotdot of dx_root before making dir indexed libaokun
2024-07-03 9:29 ` Jan Kara
2024-07-02 13:23 ` [PATCH 2/2] ext4: make sure the first directory block is not a hole libaokun
2024-07-03 9:36 ` Jan Kara [this message]
2024-07-11 13:20 ` [PATCH 0/2] ext4: fix unable to handle kernel paging request in do_split() Theodore Ts'o
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=20240703093629.bm32twullwiqmkmp@quack3 \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=libaokun1@huawei.com \
--cc=libaokun@huaweicloud.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--cc=stable@kernel.org \
--cc=syzbot+ae688d469e36fb5138d0@syzkaller.appspotmail.com \
--cc=tytso@mit.edu \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.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