From: William Dauchy <wdauchy@gmail.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Linux NFS mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/6] Fix NFSv4 client-side security autonegotiation
Date: Sun, 8 Sep 2013 16:04:21 +0200 [thread overview]
Message-ID: <CAJ75kXadApKMJVCyTV9+=HZ_93AeOv5kOn6HmHArgsG-ocPSbA@mail.gmail.com> (raw)
In-Reply-To: <1378648830.3165.2.camel@leira.trondhjem.org>
On Sun, Sep 8, 2013 at 4:00 PM, Myklebust, Trond
<Trond.Myklebust@netapp.com> wrote:
> I wasn't planning on doing that as it is easy to work around the problem
> by using an explicit 'sec=' option. That said, if the distros do want it
> in 3.10, then they should be able to sponsor its inclusion in the stable
> series.
ack, understood.
Regards,
--
William
prev parent reply other threads:[~2013-09-08 14:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-07 23:18 [PATCH 0/6] Fix NFSv4 client-side security autonegotiation Trond Myklebust
2013-09-07 23:18 ` [PATCH 1/6] NFS: Clean up the auth flavour array mess Trond Myklebust
2013-09-07 23:18 ` [PATCH 2/6] NFS: Clean up nfs_parse_security_flavors() Trond Myklebust
2013-09-07 23:18 ` [PATCH 3/6] NFSv4: Fix security auto-negotiation Trond Myklebust
2013-09-07 23:18 ` [PATCH 4/6] NFSv4: Disallow security negotiation for lookups when 'sec=' is specified Trond Myklebust
2013-09-07 23:18 ` [PATCH 5/6] NFSv4: Allow security autonegotiation for submounts Trond Myklebust
2013-09-07 23:18 ` [PATCH 6/6] NFS: nfs_compare_super shouldn't check the auth flavour unless 'sec=' was set Trond Myklebust
2013-09-08 20:22 ` [PATCH 3/6] NFSv4: Fix security auto-negotiation Chuck Lever
2013-09-08 20:50 ` Myklebust, Trond
2013-09-08 13:55 ` [PATCH 0/6] Fix NFSv4 client-side security autonegotiation William Dauchy
2013-09-08 14:00 ` Myklebust, Trond
2013-09-08 14:04 ` William Dauchy [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='CAJ75kXadApKMJVCyTV9+=HZ_93AeOv5kOn6HmHArgsG-ocPSbA@mail.gmail.com' \
--to=wdauchy@gmail.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).