From: David Howells <dhowells@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: dhowells@redhat.com, torvalds@linux-foundation.org,
keyrings@linux-nfs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KEYS: The request_key() syscall should link an existing key to the dest keyring
Date: Tue, 27 Apr 2010 11:15:06 +0100 [thread overview]
Message-ID: <17298.1272363306@redhat.com> (raw)
In-Reply-To: <20100426160918.6f624d86.akpm@linux-foundation.org>
Andrew Morton <akpm@linux-foundation.org> wrote:
> I don't think I understand that description. Are you saying that the
> patch switches things from the first example output into the second case?
request_key() system call is meant to recursively search all your keyrings for
the key you desire, and, optionally, if it doesn't exist, call out to userspace
to create one for you.
If request_key() finds or creates a key, it should, optionally, create a link
to that key from the destination keyring specified.
Therefore, if, after a successful call to request_key() with a desination
keyring specified, you see the destination keyring empty, the code didn't work
correctly.
If you see the found key in the keyring, then it did - which is what the patch
is required for.
> Is the fix needed in -stable?
Yes.
David
next prev parent reply other threads:[~2010-04-27 10:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 15:44 [PATCH] KEYS: The request_key() syscall should link an existing key to the dest keyring David Howells
2010-04-26 23:09 ` Andrew Morton
2010-04-27 10:15 ` David Howells [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-26 14:59 David Howells
2010-04-28 12:04 ` Vegard Nossum
2010-04-28 14:58 ` 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=17298.1272363306@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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