public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Tao Ma <tm@tao.ma>
To: Yongqiang Yang <xiaoqiangnk@gmail.com>
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu
Subject: Re: [PATCH] ext4: fix wrong verification in ext4_ext_insert_index
Date: Mon, 17 Oct 2011 16:49:32 +0800	[thread overview]
Message-ID: <4E9BEC1C.3050905@tao.ma> (raw)
In-Reply-To: <1318831867-8225-1-git-send-email-xiaoqiangnk@gmail.com>

Hi yongqiang,
On 10/17/2011 02:11 PM, Yongqiang Yang wrote:
> After inserting an new index, current number of indexes should
> be greater than original number by 1.  So if the new index is
> less or equal than LAST_INDEX + 1, then indexes are continugous.
> If new index will be placed on the end, then ix will equals
> LAST_INDEX + 1. Index entries has been verifiyed in pervious code
> in ext4_ext_insert_index.
Thanks for the effort. But actually this is caused by my original patch
4fd30c033, and your fix doesn't resolve the problem I want to fix. So
consider ix is already overflow, the check can't prevent it from
stamping on the memory after this extent block. I have sent another fix
for it.

Thanks
Tao
> 
> Signed-off-by: Yongqiang Yang <xiaoqiangnk@gmail.com>
> ---
>  fs/ext4/extents.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
> index 2dff31e..322398e 100644
> --- a/fs/ext4/extents.c
> +++ b/fs/ext4/extents.c
> @@ -779,7 +779,7 @@ static int ext4_ext_insert_index(handle_t *handle, struct inode *inode,
>  		ix = curp->p_idx;
>  	}
>  
> -	if (unlikely(ix > EXT_LAST_INDEX(curp->p_hdr))) {
> +	if (unlikely(ix > EXT_LAST_INDEX(curp->p_hdr) + 1)) {
>  		EXT4_ERROR_INODE(inode, "ix > EXT_LAST_INDEX!");
>  		return -EIO;
>  	}


  reply	other threads:[~2011-10-17  8:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-17  6:11 [PATCH] ext4: fix wrong verification in ext4_ext_insert_index Yongqiang Yang
2011-10-17  8:49 ` Tao Ma [this message]
2011-10-17  9:00   ` Yongqiang Yang

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=4E9BEC1C.3050905@tao.ma \
    --to=tm@tao.ma \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=xiaoqiangnk@gmail.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