From: Steve Dickson <SteveD@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: Linux Keyring Mailing list <keyrings@linux-nfs.org>,
Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] NFS: Make keys writable on the idmap keyring.
Date: Wed, 08 Feb 2012 11:34:44 -0500 [thread overview]
Message-ID: <4F32A424.20907@RedHat.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1202081029000.777@tundra.namei.org>
I'm indifferent... as long as it gets in...
Personally I thought it should been be part of David's
"KEYS: Allow special keyrings to be cleared" patch
since NFS can not use that feature unless the
key is writable...
steved.
On 02/07/2012 06:29 PM, James Morris wrote:
> Should this go in via the NFS tree? I can put it into the security tree
> otherwise.
>
>
> On Tue, 7 Feb 2012, Steve Dickson wrote:
>
>> To take advantage of the "Allow special keyrings to be
>> cleared" keyring patch the NFS keyring has to be writeable.
>>
>> Signed-off-by: Steve Dickson <steved@redhat.com>
>> ---
>> fs/nfs/idmap.c | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/fs/nfs/idmap.c b/fs/nfs/idmap.c
>> index a1bbf77..1d88cdb 100644
>> --- a/fs/nfs/idmap.c
>> +++ b/fs/nfs/idmap.c
>> @@ -269,7 +269,7 @@ static ssize_t nfs_idmap_request_key(const char *name, size_t namelen,
>> }
>>
>> rcu_read_lock();
>> - rkey->perm |= KEY_USR_VIEW;
>> + rkey->perm |= KEY_USR_VIEW|KEY_USR_WRITE;
>>
>> ret = key_validate(rkey);
>> if (ret < 0)
>> --
>> 1.7.7.5
>>
>
next prev parent reply other threads:[~2012-02-08 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 13:02 [PATCH] NFS: Make keys writable on the idmap keyring Steve Dickson
2012-02-07 23:29 ` James Morris
2012-02-08 16:34 ` Steve Dickson [this message]
2012-02-08 10:33 ` [Keyrings] " David Howells
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=4F32A424.20907@RedHat.com \
--to=steved@redhat.com \
--cc=jmorris@namei.org \
--cc=keyrings@linux-nfs.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;
as well as URLs for NNTP newsgroup(s).