public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Brian Foster <bfoster@redhat.com>, Eric Sandeen <sandeen@redhat.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfsprogs: properly terminate string in quota's restore_file()
Date: Wed, 26 Aug 2015 16:56:16 -0500	[thread overview]
Message-ID: <55DE3600.4000401@sandeen.net> (raw)
In-Reply-To: <20150826115308.GB11759@bfoster.bfoster>

On 8/26/15 6:53 AM, Brian Foster wrote:
> On Tue, Aug 25, 2015 at 11:39:29AM -0500, Eric Sandeen wrote:
>> This code copies up to the entire size of devbuffer, and then
>> tries to use "strlen" to null terminate it.
>>
>> But strlen works by *finding* the null, so it's at best a
>> no-op, and at worst not properly terminating the string.
>>
>> Fix this by placing the null at the last byte of the buffer.
>>
>> Addresses-Coverity-Id: 1297519
>> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
>> ---
>>
>> diff --git a/quota/edit.c b/quota/edit.c
>> index d226e89..a53a7e6 100644
>> --- a/quota/edit.c
>> +++ b/quota/edit.c
>> @@ -385,7 +385,7 @@ restore_file(
>>  	while (fgets(buffer, sizeof(buffer), fp) != NULL) {
>>  		if (strncmp("fs = ", buffer, 5) == 0) {
>>  			dev = strncpy(devbuffer, buffer+5, sizeof(devbuffer));
>> -			dev[strlen(dev) - 1] = '\0';
>> +			dev[sizeof(devbuffer) - 1] = '\0';
> 
> According to the man page, fgets() NULL terminates the provided buffer.

Yep, I should have looked more closely.

It copies at most size-1 (511 bytes), including the newline if it fits,
and terminates with \0.

> Next, we attempt to strncpy() just the device name part of the string
> (copying up to 512 bytes from a 512-5 byte buffer).

In fact since the original buffer (via fgets, 512) will be <= 512 long,
copying again from 5 bytes in will always result in less than 512 bytes
copied.

> I'm not quite sure,
> but it looks like the above line could be trying to replace a newline
> with a NULL terminator..? E.g., it expects the last character in an
> already NULL terminated line to be a newline.

Yes, that's exactly it, thanks.

There is one very corner case where if the last char in the buffer is
part of the device name, the buffer won't contain the newline, and the
'\0' will actually take out one char, rather than the newline.  But
that's one heck of a corner case, the exactly-sized-device-name case ...
probably not worth worrying about, though I might send a patch just to
satisfy my OCD.

Thanks for keeping me straight on this one, sorry for the noise.

-Eric

> Brian
> 
>>  			continue;
>>  		}
>>  		rtbsoft = rtbhard = 0;
>>
>> _______________________________________________
>> 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
> 

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

      reply	other threads:[~2015-08-26 21:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25 16:39 [PATCH] xfsprogs: properly terminate string in quota's restore_file() Eric Sandeen
2015-08-26 11:53 ` Brian Foster
2015-08-26 21:56   ` Eric Sandeen [this message]

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=55DE3600.4000401@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=bfoster@redhat.com \
    --cc=sandeen@redhat.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