linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rock Lee <zimilo@code-trick.com>
To: dave@jikos.cz, Rock Lee <zimilo@code-trick.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: [BUG][PATCH][BTRFS-PROGS] Bug overflow fix
Date: Fri, 26 Oct 2012 11:22:01 +0800	[thread overview]
Message-ID: <CAMRmmp+HMgd6pgHk313qQgUK7atftBTGE7rcuN9q1Agx02a3Ng@mail.gmail.com> (raw)
In-Reply-To: <20121025151801.GG10679@twin.jikos.cz>

Yeah, I will improve the patch to get it better.

Thanks,
- Rock

2012/10/25 David Sterba <dave@jikos.cz>:
> On Wed, Oct 24, 2012 at 04:24:02PM +0800, Rock Lee wrote:
>> If there's is a long name directory exists in the /dev, then an
>> overflow will hit in function utils.c btrfs_scan_one_dir:1013!
>>
>> The minimal fix is to use snprintf instead of strcpy.
>>
>> The reason why not using strncpy is that, if there is no null byte
>> among the first n bytes of src, the string  placed  in  dest
>> will not be null - terminated.
>>
>> ---
>> index 3c88d2e..7200aef 100644
>> --- a/utils.c
>> +++ b/utils.c
>> @@ -969,7 +969,7 @@ int btrfs_scan_one_dir(char *dirname, int run_ioctl)
>>       pending = malloc(sizeof(*pending));
>>       if (!pending)
>>               return -ENOMEM;
>> -     strcpy(pending->name, dirname);
>> +     snprintf(pending->name, sizeof(pending->name), "%s", dirname);
>
> pending is defined as
>
> 919 struct pending_dir {
> 920         struct list_head list;
> 921         char name[256];
> 922 };
>
> and name is supposed to hold a full path, so it should be of PATH_MAX
> (4096) size, 256 is a limit for a single filename.
>
> There's another hardcoded value for a path
>
> 971         dirname_len = strlen(pending->name);
> 972         pathlen = 1024;
> ^^^
> 973         fullpath = malloc(pathlen);
> 974         dirname = pending->name;
>
> that shuld be of PATH_MAX size.
>
> thanks,
> david

      reply	other threads:[~2012-10-26  3:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24  8:24 [BUG][PATCH][BTRFS-PROGS] Bug overflow fix Rock Lee
2012-10-25 15:18 ` David Sterba
2012-10-26  3:22   ` Rock Lee [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=CAMRmmp+HMgd6pgHk313qQgUK7atftBTGE7rcuN9q1Agx02a3Ng@mail.gmail.com \
    --to=zimilo@code-trick.com \
    --cc=dave@jikos.cz \
    --cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).