From: tytso@mit.edu
To: Jan Kara <jack@suse.cz>
Cc: <linux-ext4@vger.kernel.org>, stable@vger.kernel.org
Subject: Re: [PATCH] ext4: Fix checking of entry validity
Date: Fri, 7 Aug 2020 16:07:24 -0400 [thread overview]
Message-ID: <20200807200724.GZ7657@mit.edu> (raw)
In-Reply-To: <20200731162135.8080-1-jack@suse.cz>
Thanks, applied, although I changed the commit summary to be:
ext4: fix checking of directory entry validity for inline directories
- Ted
On Fri, Jul 31, 2020 at 06:21:35PM +0200, Jan Kara wrote:
> ext4_search_dir() and ext4_generic_delete_entry() can be called both for
> standard director blocks and for inline directories stored inside inode
> or inline xattr space. For the second case we didn't call
> ext4_check_dir_entry() with proper constraints that could result in
> accepting corrupted directory entry as well as false positive filesystem
> errors like:
>
> EXT4-fs error (device dm-0): ext4_search_dir:1395: inode #28320400:
> block 113246792: comm dockerd: bad entry in directory: directory entry too
> close to block end - offset=0, inode=28320403, rec_len=32, name_len=8,
> size=4096
>
> Fix the arguments passed to ext4_check_dir_entry().
>
> Fixes: 109ba779d6cc ("ext4: check for directory entries too close to block end")
> CC: stable@vger.kernel.org
> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
> fs/ext4/namei.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
next prev parent reply other threads:[~2020-08-07 20:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 16:21 [PATCH] ext4: Fix checking of entry validity Jan Kara
2020-08-01 23:18 ` Sasha Levin
2020-08-06 1:24 ` Sasha Levin
2020-08-07 20:07 ` tytso [this message]
2020-08-09 15:53 ` Sasha Levin
2020-08-13 16:25 ` Sasha Levin
2020-08-19 23:56 ` Sasha Levin
2020-08-26 13:53 ` Sasha Levin
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=20200807200724.GZ7657@mit.edu \
--to=tytso@mit.edu \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=stable@vger.kernel.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.