public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: green@linuxhacker.ru
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	devel@driverdev.osuosl.org,
	Andreas Dilger <andreas.dilger@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] staging/lustre/llite: fix ll_getname user buffer copy
Date: Wed, 10 Jun 2015 10:52:09 +0300	[thread overview]
Message-ID: <20150610075209.GC28762@mwanda> (raw)
In-Reply-To: <1433911283-24902-3-git-send-email-green@linuxhacker.ru>

On Wed, Jun 10, 2015 at 12:41:23AM -0400, green@linuxhacker.ru wrote:
> From: Oleg Drokin <green@linuxhacker.ru>
> 
> strncpy_from_user could return negative values on error,
> so need to take those into account.
> Since ll_getname is used to get a single component name from userspace
> to transfer to server as-is, there's no need to allocate 4k buffer
> as done by __getname. Allocate NAME_MAX+1 buffer instead to ensure
> we have enough for a null terminated max valid length buffer.
> 
> This was discovered by Al Viro in https://lkml.org/lkml/2015/4/11/243
> 
> Signed-off-by: Oleg Drokin <green@linuxhacker.ru>
> ---
>  drivers/staging/lustre/lustre/llite/dir.c | 20 +++++++++++---------
>  1 file changed, 11 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/staging/lustre/lustre/llite/dir.c b/drivers/staging/lustre/lustre/llite/dir.c
> index 87a042c..e0b9043 100644
> --- a/drivers/staging/lustre/lustre/llite/dir.c
> +++ b/drivers/staging/lustre/lustre/llite/dir.c
> @@ -1213,29 +1213,31 @@ out:
>  	return rc;
>  }
>  
> -static char *
> -ll_getname(const char __user *filename)
> +/* This function tries to get a single name component,
> + * to send to the server. No actual path traversal involved,
> + * so we limit to NAME_MAX */
> +static char *ll_getname(const char __user *filename)
>  {
>  	int ret = 0, len;
> -	char *tmp = __getname();
> +	char *tmp = kzalloc(NAME_MAX + 1, GFP_KERNEL);

Doing allocations in the declaration block is rare in the kernel but it
accounts for around a quarter of the missing NULL checks and many memory
leaks in the kbuild zero day bot testing.  It's a bad idea and some
subsystems ban the practice, but Greg is fine with it so I'm not going
to complain.

This is me keeping totally silent like a mouse.  :P

>  
>  	if (!tmp)
>  		return ERR_PTR(-ENOMEM);
>  
> -	len = strncpy_from_user(tmp, filename, PATH_MAX);
> -	if (len == 0)
> +	len = strncpy_from_user(tmp, filename, NAME_MAX);
> +	if (len < 0)
> +		ret = len;
> +	else if (len == 0)
>  		ret = -ENOENT;
> -	else if (len > PATH_MAX)
> -		ret = -ENAMETOOLONG;

I don't like how this does silent truncation.  strncpy_from_user()
return -EFAULT if we run into unmapped memory.  Otherwise if the user
supplies a too long name it returns len == PATH_MAX.  (I think, the
documentation for this function is hard to understand).

Of course, the check was never true in the original code...

regards,
dan carpenter


  reply	other threads:[~2015-06-10  7:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10  4:41 [PATCH 0/2] Fixup lusre ll_getname green
2015-06-10  4:41 ` [PATCH 1/2] staging/lustre/llite: remove LL_IOC_REMOVE_ENTRY handler green
2015-06-10  7:08   ` Sudip Mukherjee
2015-06-10  7:19     ` Oleg Drokin
2015-06-10  4:41 ` [PATCH 2/2] staging/lustre/llite: fix ll_getname user buffer copy green
2015-06-10  7:52   ` Dan Carpenter [this message]
2015-06-10  7:59     ` Oleg Drokin

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=20150610075209.GC28762@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=andreas.dilger@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=green@linuxhacker.ru \
    --cc=gregkh@linuxfoundation.org \
    --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