From: Seth Forshee <seth.forshee@canonical.com>
To: David Howells <dhowells@redhat.com>
Cc: viro@ZenIV.linux.org.uk, linux-kernel@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
linux-fsdevel@vger.kernel.org, linux-afs@lists.infradead.org
Subject: Re: [PATCH] vfs: Partially revert addition of cred override in follow_automount()
Date: Wed, 22 Feb 2017 09:17:58 -0600 [thread overview]
Message-ID: <20170222151758.GB29966@ubuntu-hedt> (raw)
In-Reply-To: <148777059228.7183.7698026974948697349.stgit@warthog.procyon.org.uk>
On Wed, Feb 22, 2017 at 01:36:32PM +0000, David Howells wrote:
> The following commit:
>
> commit aeaa4a79ff6a5ed912b7362f206cf8576fca538b
> Author: Eric W. Biederman <ebiederm@xmission.com>
> Date: Sat Jul 23 11:20:44 2016 -0500
> fs: Call d_automount with the filesystems creds
>
> brackets the call to ->d_automount() with override_creds() and
> revert_creds(), setting the initial credentials for use whilst
> automounting.
>
> This, however, breaks AFS as it's no longer able to access the calling
> process's keyrings to read the destination on a mountpoint. This has gone
> unnoticed till now because, to this point, stat'ing or validating the inode
> caused the body of the mountpoint to be read into the pagecache (so that we
> could determine whether what we were looking at was really a mountpoint).
>
> However, the page containing the mountpoint destination is merely *cached*
> and not pinned. If it gets discarded and we try to read it in d_automount,
> we may fail because we have no authentication tokens available.
>
> So, for the moment, revert the addition of override_creds() and
> revert_creds() and their variable.
>
> Fixes: aeaa4a79ff6a ("fs: Call d_automount with the filesystems creds")
> Signed-off-by: David Howells <dhowells@redhat.com>
> cc: Seth Forshee <seth.forshee@canonical.com>
> cc: "Eric W. Biederman" <ebiederm@xmission.com>
> cc: Al Viro <viro@ZenIV.linux.org.uk>
Eric's already applied a patch that should fix this problem. As far as I
know it's only been tested against NFS though, so you might want to test
that it also fixes the issue with AFS.
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=93faccbbfa958a9668d3ab4e30f38dd205cee8d8
Thanks,
Seth
prev parent reply other threads:[~2017-02-22 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 13:36 [PATCH] vfs: Partially revert addition of cred override in follow_automount() David Howells
2017-02-22 15:17 ` David Howells
2017-02-22 15:17 ` Seth Forshee [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=20170222151758.GB29966@ubuntu-hedt \
--to=seth.forshee@canonical.com \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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