linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: linux-nfs@vger.kernel.org
Cc: tibbs@math.uh.edu
Subject: Re: RFC: make labeled NFS opt-in
Date: Wed, 11 Jan 2017 21:17:03 -0500	[thread overview]
Message-ID: <20170112021703.GC18977@fieldses.org> (raw)
In-Reply-To: <20170104165636.GA17649@fieldses.org>

On Wed, Jan 04, 2017 at 11:56:36AM -0500, bfields wrote:
> This is something I should have noticed before merging labeled NFS:
> labeled NFS shouldn't be on by default, among other reasons because it
> assumes everybody's using consistent security policies.  As 4.2 is
> getting turned on by default, this is starting to generate bug reports.
> 
> The patch below turns it off by default, and provides a new option to
> turn it on per export.  The drawback is a regression on kernel upgrade
> for anyone depending on labeled NFS, until they find the new option.  My
> impression is that's a specialized use case that still has a small
> number of users at this point, so I think we can get away with that.
> 
> The below is untested.  I have a (small) nfs-utils patch as well.

OK, I've tested now, the only problem was actually a preexisting
bug--I'll post the patches, plus the companion nfs-utils patch.

--b.

  reply	other threads:[~2017-01-12  2:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04 16:56 RFC: make labeled NFS opt-in J. Bruce Fields
2017-01-12  2:17 ` J. Bruce Fields [this message]
2017-01-12 15:29   ` Andy Adamson
2017-01-12 16:10     ` J. Bruce Fields
2017-01-12 16:51       ` Andy Adamson

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=20170112021703.GC18977@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=tibbs@math.uh.edu \
    /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).