All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Allison <jra@samba.org>
To: Jeff Layton <jeff.layton@primarydata.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	linux-fsdevel@vger.kernel.org,
	Benjamin Coddington <bcodding@redhat.com>,
	Dmitry Vyukov <dvyukov@google.com>,
	Linux Containers <containers@lists.linux-foundation.org>
Subject: Re: [RFC][PATCH] locks: Allow disabling mandatory locking at compile time
Date: Wed, 11 Nov 2015 14:46:35 -0800	[thread overview]
Message-ID: <20151111224635.GD13853@jra3> (raw)
In-Reply-To: <20151111174401.5778153c@tlielax.poochiereds.net>

On Wed, Nov 11, 2015 at 05:44:01PM -0500, Jeff Layton wrote:
> Windows BRLs are mandatory but they have totally different semantics.
> 
> I think there is little reason to keep POSIX mandatory locks for
> windows emulation purposes. I'm pretty sure Samba doesn't rely on them,
> for instance, given that you have to use a funky mode bit combo to
> enable them.

Nope. We emulate Windows mandatory locks on top of POSIX advisory
locks. We don't use POSIX mandatory locks at all.

  parent reply	other threads:[~2015-11-11 22:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11 17:49 [RFC][PATCH] locks: Allow disabling mandatory locking at compile time Eric W. Biederman
2015-11-11 17:49 ` Eric W. Biederman
     [not found] ` <876118v333.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2015-11-11 20:26   ` J. Bruce Fields
2015-11-11 20:26 ` J. Bruce Fields
     [not found]   ` <20151111202607.GD29410-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2015-11-11 22:44     ` Jeff Layton
2015-11-11 22:44   ` Jeff Layton
     [not found]     ` <20151111174401.5778153c-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2015-11-11 22:46       ` Jeremy Allison via Containers
2015-11-11 23:22       ` Eric W. Biederman
2015-11-11 22:46     ` Jeremy Allison [this message]
2015-11-11 23:22     ` Eric W. Biederman
     [not found]       ` <876118ruiu.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2015-11-12  1:33         ` J. Bruce Fields
2015-11-16 14:58         ` Jeff Layton
2015-11-16 14:58           ` Jeff Layton
2015-11-16 21:34           ` Eric W. Biederman
     [not found]           ` <20151116095841.0f620a5c-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2015-11-16 21:34             ` Eric W. Biederman
2015-11-12  1:33       ` J. Bruce Fields
     [not found]         ` <20151112013311.GA32064-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2015-11-12  1:55           ` 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=20151111224635.GD13853@jra3 \
    --to=jra@samba.org \
    --cc=bcodding@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=containers@lists.linux-foundation.org \
    --cc=dvyukov@google.com \
    --cc=ebiederm@xmission.com \
    --cc=jeff.layton@primarydata.com \
    --cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.