public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: rjohnston@sgi.com, xfs@oss.sgi.com
Subject: Re: [PATCH] xfsdump: prevent segfault in cb_add_inogrp
Date: Wed, 26 Aug 2015 11:42:08 -0500	[thread overview]
Message-ID: <55DDEC60.4040509@sandeen.net> (raw)
In-Reply-To: <20150924193241.975348815@gulag1.americas.sgi.com>

On 8/26/15 9:33 AM, rjohnston@sgi.com wrote:
> The call to memset will segfault because the offset for the first
> parameter is done twice. We are using pointer math to do the
> calculation.
> The first time is when calculating oldsize, the size of i2gseg_t
> is accounted for.
> 	oldsize = (numsegs - SEGPERHNK) * sizeof(i2gseg_t);
> Then in the call to memset, oldsize is again multiplied by the size
> of i2gmap_t.
> 	memset(inomap.i2gmap + oldsize, ...)
> 	
> i2gmap holds the used inodes in each chunk. When there are 2^31 chunk
> entries, it could describe 2^31 (1 inode/chunk)- 2^40 (64 inodes/chunk).
> 
> With 100s of millions of inodes there are enough entries to wrap the
> 32 bit variable oldsize.
> 
> Switching to use array index notation instead of calculating the
> pointer address twice ;) would resolve this issue. The unneeded
> local variable oldsize can be removed as well.

Ok, this doesn't explain the type change for numsegs, does it?

Can you walk me through why that's needed?  At what point would
numsegs = inomap.hnkmaplen * SEGPERHNK; overflow?

Thanks,
-Eric

> ---
>  dump/inomap.c |    8 ++------
>  1 file changed, 2 insertions(+), 6 deletions(-)
> 
> Index: b/dump/inomap.c
> ===================================================================
> --- a/dump/inomap.c
> +++ b/dump/inomap.c
> @@ -1125,8 +1125,7 @@ cb_add_inogrp( void *arg1, intgen_t fsfd
>  		lastsegp->segoff = 0;
>  
>  		if (lastsegp->hnkoff == inomap.hnkmaplen) {
> -			intgen_t numsegs;
> -			intgen_t oldsize;
> +			int64_t numsegs;
>  
>  			inomap.hnkmaplen++;
>  			inomap.hnkmap = (hnk_t *)
> @@ -1140,10 +1139,7 @@ cb_add_inogrp( void *arg1, intgen_t fsfd
>  				return -1;
>  
>  			/* zero the new portion of the i2gmap */
> -			oldsize = (numsegs - SEGPERHNK) * sizeof(i2gseg_t);
> -
> -			memset(inomap.i2gmap + oldsize,
> -			       0,
> +			memset(&inomap.i2gmap[numsegs - SEGPERHNK], 0,
>  			       SEGPERHNK * sizeof(i2gseg_t));
>  		}
>  
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
> 

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2015-08-26 16:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-26 14:33 [PATCH] xfsdump: prevent segfault in cb_add_inogrp rjohnston
2015-08-26 16:42 ` Eric Sandeen [this message]
2015-08-26 17:10   ` Rich Johnston
2015-08-26 21:26     ` Dave Chinner
2015-08-26 17:36 ` [PATCH V2] " rjohnston
2015-08-26 21:37   ` Dave Chinner
2015-08-26 21:57     ` Rich Johnston
2015-08-26 22:19       ` Eric Sandeen
2015-08-26 22:27         ` Eric Sandeen
2015-08-26 22:21       ` Dave Chinner
2015-08-26 22:29 ` [PATCH V3] " rjohnston
2015-08-26 22:56   ` Dave Chinner
2015-08-26 22:58     ` Rich Johnston
2015-09-21 13:42       ` Rich Johnston
2015-08-26 23:00   ` Eric Sandeen

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=55DDEC60.4040509@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=rjohnston@sgi.com \
    --cc=xfs@oss.sgi.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