From: David Howells <dhowells@redhat.com>
To: linux-security-module@vger.kernel.org
Subject: Re: [PATCH] KEYS: remove unnecessary get/put of explicit dest_keyring
Date: Fri, 24 Nov 2017 21:24:30 +0000 [thread overview]
Message-ID: <5687.1511558670@warthog.procyon.org.uk> (raw)
In-Reply-To: <20171120225757.96498-1-ebiggers3@gmail.com>
Eric Biggers <ebiggers3@gmail.com> wrote:
> if (dest_keyring) {
> - construct_get_dest_keyring(&dest_keyring);
Actually, I think I have the order of these lines inverted.
construct_get_dest_keyring() can actually return without setting dest_keyring
to anything. This didn't used to be the case, but now that the user-session
keyring is made lazily, there's no guaranteed fallback.
David
WARNING: multiple messages have this Message-ID (diff)
From: dhowells@redhat.com (David Howells)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] KEYS: remove unnecessary get/put of explicit dest_keyring
Date: Fri, 24 Nov 2017 21:24:30 +0000 [thread overview]
Message-ID: <5687.1511558670@warthog.procyon.org.uk> (raw)
In-Reply-To: <20171120225757.96498-1-ebiggers3@gmail.com>
Eric Biggers <ebiggers3@gmail.com> wrote:
> if (dest_keyring) {
> - construct_get_dest_keyring(&dest_keyring);
Actually, I think I have the order of these lines inverted.
construct_get_dest_keyring() can actually return without setting dest_keyring
to anything. This didn't used to be the case, but now that the user-session
keyring is made lazily, there's no guaranteed fallback.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: David Howells <dhowells@redhat.com>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: dhowells@redhat.com, keyrings@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH] KEYS: remove unnecessary get/put of explicit dest_keyring
Date: Fri, 24 Nov 2017 21:24:30 +0000 [thread overview]
Message-ID: <5687.1511558670@warthog.procyon.org.uk> (raw)
In-Reply-To: <20171120225757.96498-1-ebiggers3@gmail.com>
Eric Biggers <ebiggers3@gmail.com> wrote:
> if (dest_keyring) {
> - construct_get_dest_keyring(&dest_keyring);
Actually, I think I have the order of these lines inverted.
construct_get_dest_keyring() can actually return without setting dest_keyring
to anything. This didn't used to be the case, but now that the user-session
keyring is made lazily, there's no guaranteed fallback.
David
next prev parent reply other threads:[~2017-11-24 21:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 22:57 [PATCH] KEYS: remove unnecessary get/put of explicit dest_keyring Eric Biggers
2017-11-20 22:57 ` Eric Biggers
2017-11-20 22:57 ` Eric Biggers
2017-11-24 15:52 ` David Howells
2017-11-24 15:52 ` David Howells
2017-11-24 15:52 ` David Howells
2017-11-24 20:37 ` Eric Biggers
2017-11-24 20:37 ` Eric Biggers
2017-11-24 20:37 ` Eric Biggers
2017-11-24 21:18 ` David Howells
2017-11-24 21:18 ` David Howells
2017-11-24 21:18 ` David Howells
2017-11-24 21:24 ` David Howells [this message]
2017-11-24 21:24 ` David Howells
2017-11-24 21:24 ` 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=5687.1511558670@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-security-module@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.