From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: John Hughes <john@Calva.COM>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add "-e" option to rpc.gssd to allow error on ticket expiry. Try 2 with added man pages.
Date: Fri, 18 Nov 2011 20:35:33 +0200 [thread overview]
Message-ID: <1321641333.2653.15.camel@lade.trondhjem.org> (raw)
In-Reply-To: <4EC66D12.2090505@Calva.COM>
On Fri, 2011-11-18 at 15:34 +0100, John Hughes wrote:
> Description: Add "-e" (ticket expiry is error) option to rpc.gssd
> In kernels starting around 2.6.34 the nfs4 server will block all I/O
> when a user ticket expires. In earlier kernels the I/O would fail
> with an EACCESS error. This patch adds a "-e" option to rpc.gssd
> which allow the earlier behaviour (EKEYEXPIRED is converted to
> EACCESS). This behaviour is particularly useful when user home
> directories are nfs4 mounted with krb5 security - if the user is
> absent from their workstation for long enough for the ticket to
> expire a new ticket will be obtained (via pam_krb5) by the screen
> unlock process.
You need a big fat warning somewhere that enabling this option WILL
cause data corruption...
Trond
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2011-11-18 18:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 14:34 [PATCH] Add "-e" option to rpc.gssd to allow error on ticket expiry. Try 2 with added man pages John Hughes
2011-11-18 18:35 ` Trond Myklebust [this message]
2011-11-18 19:19 ` John Hughes
2011-11-18 20:33 ` Trond Myklebust
2011-11-18 20:47 ` Nick Bowler
2011-11-18 20:54 ` Trond Myklebust
2011-11-18 20:57 ` Jim Rees
2011-11-18 21:03 ` Trond Myklebust
2011-11-18 22:33 ` John Hughes
2011-11-18 22:37 ` Trond Myklebust
2011-11-18 22:46 ` John Hughes
2011-11-18 22:08 ` John Hughes
2011-11-18 22:38 ` Trond Myklebust
2011-11-18 22:57 ` John Hughes
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=1321641333.2653.15.camel@lade.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=john@Calva.COM \
--cc=linux-kernel@vger.kernel.org \
--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