From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: zohar@linux.vnet.ibm.com, safford@us.ibm.com
Cc: dhowells@redhat.com, james.l.morris@oracle.com, serge@hallyn.com,
linux-security-module@vger.kernel.org, keyrings@linux-nfs.org,
linux-kernel@vger.kernel.org,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Subject: [PATCH] keys, encrypted: add forgotten newline characters
Date: Fri, 15 Aug 2014 09:18:56 +0300 [thread overview]
Message-ID: <1408083536-8578-1-git-send-email-jarkko.sakkinen@linux.intel.com> (raw)
I was debugging patches that I'm working for trusted keys.
I have a test case where I seal an encrypted key with a trusted
key. Piping of the encrypted key failed but I couldn't see any
error message from the encrypted subsystem. Then I tried my
test a second time and error message was visible in klog.
The root cause was the forgotten newline characters. This patch
fixes the issue.
Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
---
security/keys/encrypted-keys/encrypted.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/security/keys/encrypted-keys/encrypted.c b/security/keys/encrypted-keys/encrypted.c
index 5fe443d..406f6cb 100644
--- a/security/keys/encrypted-keys/encrypted.c
+++ b/security/keys/encrypted-keys/encrypted.c
@@ -447,10 +447,10 @@ static struct key *request_master_key(struct encrypted_key_payload *epayload,
int ret = PTR_ERR(mkey);
if (ret == -ENOTSUPP)
- pr_info("encrypted_key: key %s not supported",
+ pr_info("encrypted_key: key %s not supported\n",
epayload->master_desc);
else
- pr_info("encrypted_key: key %s not found",
+ pr_info("encrypted_key: key %s not found\n",
epayload->master_desc);
goto out;
}
--
1.9.1
reply other threads:[~2014-08-15 6:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1408083536-8578-1-git-send-email-jarkko.sakkinen@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=dhowells@redhat.com \
--cc=james.l.morris@oracle.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=safford@us.ibm.com \
--cc=serge@hallyn.com \
--cc=zohar@linux.vnet.ibm.com \
/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
all inboxes | Powered by JetHome®