linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, neilb@suse.de
Subject: Re: [PATCH] locks: require that flock->l_pid be set to 0 for file-private locks
Date: Tue, 4 Mar 2014 14:22:12 -0500	[thread overview]
Message-ID: <20140304192212.GF12805@fieldses.org> (raw)
In-Reply-To: <1393960148-18802-1-git-send-email-jlayton@redhat.com>

On Tue, Mar 04, 2014 at 02:09:08PM -0500, Jeff Layton wrote:
> Neil Brown suggested potentially overloading the l_pid value as a "lock
> context" field for file-private locks. While I don't think we will
> probably want to do that here, it's probably a good idea to ensure that
> in the future we could extend this API without breaking existing
> callers.
> 
> Typically the l_pid value is ignored for incoming struct flock
> arguments, serving mainly as a place to return the pid of the owner if
> there is a conflicting lock. For file-private locks, require that it
> currently be set to 0 and return EINVAL if it isn't. If we eventually
> want to make a non-zero l_pid mean something, then this will help ensure
> that we don't break legacy programs that are using file-private locks.

Makes sense to me.

But, could you add move most of this initialization to a helper
function?  Or, better, just add it to flock64_to_posix_lock?  That would
a) remove some code duplication, and b) give a single place to add a
comment documenting the above rationale for the new check.

--b.

> 
> Cc: Neil Brown <neilb@suse.de>
> Signed-off-by: Jeff Layton <jlayton@redhat.com>
> ---
>  fs/locks.c | 24 ++++++++++++++++++++++++
>  1 file changed, 24 insertions(+)
> 
> diff --git a/fs/locks.c b/fs/locks.c
> index ce93815b0626..6fdf26a79cc8 100644
> --- a/fs/locks.c
> +++ b/fs/locks.c
> @@ -1931,6 +1931,10 @@ int fcntl_getlk(struct file *filp, unsigned int cmd, struct flock __user *l)
>  		goto out;
>  
>  	if (cmd == F_GETLKP) {
> +		error = -EINVAL;
> +		if (flock.l_pid != 0)
> +			goto out;
> +
>  		cmd = F_GETLK;
>  		file_lock.fl_flags |= FL_FILE_PVT;
>  		file_lock.fl_owner = (fl_owner_t)filp;
> @@ -2062,11 +2066,19 @@ again:
>  	 */
>  	switch (cmd) {
>  	case F_SETLKP:
> +		error = -EINVAL;
> +		if (flock.l_pid != 0)
> +			goto out;
> +
>  		cmd = F_SETLK;
>  		file_lock->fl_flags |= FL_FILE_PVT;
>  		file_lock->fl_owner = (fl_owner_t)filp;
>  		break;
>  	case F_SETLKPW:
> +		error = -EINVAL;
> +		if (flock.l_pid != 0)
> +			goto out;
> +
>  		cmd = F_SETLKW;
>  		file_lock->fl_flags |= FL_FILE_PVT;
>  		file_lock->fl_owner = (fl_owner_t)filp;
> @@ -2121,6 +2133,10 @@ int fcntl_getlk64(struct file *filp, unsigned int cmd, struct flock64 __user *l)
>  		goto out;
>  
>  	if (cmd == F_GETLKP) {
> +		error = -EINVAL;
> +		if (flock.l_pid != 0)
> +			goto out;
> +
>  		cmd = F_GETLK64;
>  		file_lock.fl_flags |= FL_FILE_PVT;
>  		file_lock.fl_owner = (fl_owner_t)filp;
> @@ -2185,11 +2201,19 @@ again:
>  	 */
>  	switch (cmd) {
>  	case F_SETLKP:
> +		error = -EINVAL;
> +		if (flock.l_pid != 0)
> +			goto out;
> +
>  		cmd = F_SETLK64;
>  		file_lock->fl_flags |= FL_FILE_PVT;
>  		file_lock->fl_owner = (fl_owner_t)filp;
>  		break;
>  	case F_SETLKPW:
> +		error = -EINVAL;
> +		if (flock.l_pid != 0)
> +			goto out;
> +
>  		cmd = F_SETLKW64;
>  		file_lock->fl_flags |= FL_FILE_PVT;
>  		file_lock->fl_owner = (fl_owner_t)filp;
> -- 
> 1.8.5.3
> 

  reply	other threads:[~2014-03-04 19:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04 19:09 [PATCH] locks: require that flock->l_pid be set to 0 for file-private locks Jeff Layton
2014-03-04 19:22 ` J. Bruce Fields [this message]
2014-03-04 20:00   ` Jeff Layton

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=20140304192212.GF12805@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=jlayton@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).