public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: zhong jiang <zhongjiang@huawei.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: <linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<jslaby@suse.cz>, <bfields@fieldses.org>,
	<viro@zeniv.linux.org.uk>, <dhowells@redhat.com>
Subject: Re: [PATCH] fs/fcntl: return -ESRCH in f_setown when pid/pgid can't be found
Date: Thu, 15 Jun 2017 09:54:07 +0800	[thread overview]
Message-ID: <5941E8BF.2070304@huawei.com> (raw)
In-Reply-To: <20170614145255.7767-1-jlayton@redhat.com>

yes,  look good to me.

but I found the another issue.  if the pass argument  is -1.  by the spec describe,
type should be assigned to PIDTYPE_MAX,  Do you think that it deserve another patch ?

Thanks
zhongjiang

On 2017/6/14 22:52, Jeff Layton wrote:
> The current implementation of F_SETOWN doesn't properly vet the argument
> passed in. It never returns an error. If the argument doesn't specify a
> valid pid/pgid, then we just end up cleaning out the file->f_owner
> structure.
>
> What we really want is to only clean that out only in the case where
> userland passed in an argument of 0. For anything else, we want to
> return ESRCH if it doesn't refer to a valid pid.
>
> The relevant POSIX spec page is here:
>
>     http://pubs.opengroup.org/onlinepubs/9699919799/functions/fcntl.html
>
> Cc: Jiri Slaby <jslaby@suse.cz>
> Cc: zhong jiang <zhongjiang@huawei.com>
> Signed-off-by: Jeff Layton <jlayton@redhat.com>
> ---
>  fs/fcntl.c | 18 +++++++++++++-----
>  1 file changed, 13 insertions(+), 5 deletions(-)
>
> diff --git a/fs/fcntl.c b/fs/fcntl.c
> index 693322e28751..afed3b364979 100644
> --- a/fs/fcntl.c
> +++ b/fs/fcntl.c
> @@ -112,8 +112,9 @@ EXPORT_SYMBOL(__f_setown);
>  int f_setown(struct file *filp, unsigned long arg, int force)
>  {
>  	enum pid_type type;
> -	struct pid *pid;
> -	int who = arg;
> +	struct pid *pid = NULL;
> +	int who = arg, ret = 0;
> +
>  	type = PIDTYPE_PID;
>  	if (who < 0) {
>  		/* avoid overflow below */
> @@ -123,12 +124,19 @@ int f_setown(struct file *filp, unsigned long arg, int force)
>  		type = PIDTYPE_PGID;
>  		who = -who;
>  	}
> +
>  	rcu_read_lock();
> -	pid = find_vpid(who);
> -	__f_setown(filp, pid, type, force);
> +	if (who) {
> +		pid = find_vpid(who);
> +		if (!pid)
> +			ret = -ESRCH;
> +	}
> +
> +	if (!ret)
> +		__f_setown(filp, pid, type, force);
>  	rcu_read_unlock();
>  
> -	return 0;
> +	return ret;
>  }
>  EXPORT_SYMBOL(f_setown);
>  

      reply	other threads:[~2017-06-15  1:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14 14:52 [PATCH] fs/fcntl: return -ESRCH in f_setown when pid/pgid can't be found Jeff Layton
2017-06-15  1:54 ` zhong jiang [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=5941E8BF.2070304@huawei.com \
    --to=zhongjiang@huawei.com \
    --cc=bfields@fieldses.org \
    --cc=dhowells@redhat.com \
    --cc=jlayton@redhat.com \
    --cc=jslaby@suse.cz \
    --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