From: Sasha Levin <sasha.levin@oracle.com>
To: linux-kernel@vger.kernel.org
Cc: Alexander Viro <viro@zeniv.linux.org.uk>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2] vfs: read file_handle only once in handle_to_path
Date: Thu, 30 Apr 2015 11:04:04 -0400 [thread overview]
Message-ID: <55424464.9030906@oracle.com> (raw)
In-Reply-To: <1422477048-4550-1-git-send-email-sasha.levin@oracle.com>
ping?
On 01/28/2015 03:30 PM, Sasha Levin wrote:
> We used to read file_handle twice. Once to get the amount of extra bytes, and
> once to fetch the entire structure.
>
> This may be problematic since we do size verifications only after the first
> read, so if the number of extra bytes changes in userspace between the first
> and second calls, we'll have an incoherent view of file_handle.
>
> Instead, read the constant size once, and copy that over to the final
> structure without having to re-read it again.
>
> Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
> ---
> Change in v2:
> - Use the f_handle pointer rather than size of struct
>
> fs/fhandle.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/fs/fhandle.c b/fs/fhandle.c
> index 999ff5c..d59712d 100644
> --- a/fs/fhandle.c
> +++ b/fs/fhandle.c
> @@ -195,8 +195,9 @@ static int handle_to_path(int mountdirfd, struct file_handle __user *ufh,
> goto out_err;
> }
> /* copy the full handle */
> - if (copy_from_user(handle, ufh,
> - sizeof(struct file_handle) +
> + *handle = f_handle;
> + if (copy_from_user(&handle->f_handle,
> + &ufh->f_handle,
> f_handle.handle_bytes)) {
> retval = -EFAULT;
> goto out_handle;
>
next prev parent reply other threads:[~2015-04-30 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 20:30 [PATCH v2] vfs: read file_handle only once in handle_to_path Sasha Levin
2015-04-30 15:04 ` Sasha Levin [this message]
2015-06-02 15:23 ` Sasha Levin
2015-06-02 17:23 ` Linus Torvalds
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=55424464.9030906@oracle.com \
--to=sasha.levin@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).