From: Josef Bacik <josef@redhat.com>
To: Jim Meyering <jim@meyering.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Josef Bacik <josef@redhat.com>
Subject: Re: [PATCH] Btrfs: NUL-terminate path buffer in DEV_INFO ioctl result
Date: Thu, 26 Apr 2012 14:26:13 -0400 [thread overview]
Message-ID: <20120426182612.GC1890@localhost.localdomain> (raw)
In-Reply-To: <87pqauwitz.fsf@rho.meyering.net>
On Thu, Apr 26, 2012 at 06:36:56PM +0200, Jim Meyering wrote:
>
> A device with name of length BTRFS_DEVICE_PATH_NAME_MAX or longer
> would not be NUL-terminated in the DEV_INFO ioctl result buffer.
>
> Signed-off-by: Jim Meyering <meyering@redhat.com>
> ---
> fs/btrfs/ioctl.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
> index 18cc23d..1578676 100644
> --- a/fs/btrfs/ioctl.c
> +++ b/fs/btrfs/ioctl.c
> @@ -2258,16 +2258,17 @@ static long btrfs_ioctl_dev_info(struct btrfs_root *root, void __user *arg)
> goto out;
> }
>
> di_args->devid = dev->devid;
> di_args->bytes_used = dev->bytes_used;
> di_args->total_bytes = dev->total_bytes;
> memcpy(di_args->uuid, dev->uuid, sizeof(di_args->uuid));
> strncpy(di_args->path, dev->name, sizeof(di_args->path));
> + di_args->path[sizeof(di_args->path) - 1] = 0;
>
> out:
> if (ret == 0 && copy_to_user(arg, di_args, sizeof(*di_args)))
> ret = -EFAULT;
>
> kfree(di_args);
> return ret;
> }
> --
> 1.7.10.336.gc5e31
This didn't merge quite right onto btrfs-next btw so I've fixed it up manually
(but left the log/author/signed off intact). Thanks,
Josef
prev parent reply other threads:[~2012-04-26 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 16:36 [PATCH] Btrfs: NUL-terminate path buffer in DEV_INFO ioctl result Jim Meyering
2012-04-26 18:22 ` Josef Bacik
2012-04-26 18:26 ` Josef Bacik [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=20120426182612.GC1890@localhost.localdomain \
--to=josef@redhat.com \
--cc=jim@meyering.net \
--cc=linux-kernel@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