All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rich Johnston <rjohnston@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH V2] xfsdump: prevent segfault in cb_add_inogrp
Date: Wed, 26 Aug 2015 16:57:37 -0500	[thread overview]
Message-ID: <55DE3651.5030803@sgi.com> (raw)
In-Reply-To: <20150826213746.GC3902@dastard>

Dave,

On 08/26/2015 04:37 PM, Dave Chinner wrote:
> On Wed, Aug 26, 2015 at 12:36:42PM -0500, 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.
>>
Per your other comment I will add a bounds check after calculating numsegs:
	if (numsegs < 0)
		return -1;

The description above will change to:

Adding a bounds check (numsegs < 0) and 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.

>> numsegs is used to calculate an array index, change it from a
>> signed int (intgen_t) to an unsigned (uint32_t).
>
I will remove the above description and leave it as is (intgen_t)
> Description does not match code:
>
>> -			intgen_t numsegs;
>> -			intgen_t oldsize;
>> +			int32_t numsegs;
>
> It's still a signed int here. And, really, just a plain old "int" is
> fine here.
>
> Cheers,
>
> Dave.
>

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

  reply	other threads:[~2015-08-26 21:57 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
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 [this message]
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=55DE3651.5030803@sgi.com \
    --to=rjohnston@sgi.com \
    --cc=david@fromorbit.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 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.