From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: dhowells@redhat.com, linux-crypto@vger.kernel.org
Cc: sowmini.varadhan@oracle.com
Subject: unaligned access in pkcs7_verify
Date: Fri, 2 Oct 2015 10:00:14 -0400 [thread overview]
Message-ID: <20151002140014.GI18263@oracle.com> (raw)
Hi,
I'm getting a lot of unaligned access messages each time I
do "modprobe [-r] <module>" on sparc:
Kernel unaligned access at TPC[6ad9b4] pkcs7_verify+0x1ec/0x5e0
Kernel unaligned access at TPC[6a5484] crypto_shash_finup+0xc/0x5c
Kernel unaligned access at TPC[6a5390] crypto_shash_update+0xc/0x54
Kernel unaligned access at TPC[10150308] sha1_sparc64_update+0x14/0x5c [sha1_sparc64]
Kernel unaligned access at TPC[101501ac] __sha1_sparc64_update+0xc/0x98 [sha1_sparc64]
Looks like these are being caused by an unaligned desc at
desc = digest + digest_size;
Doing this:
--- a/crypto/asymmetric_keys/pkcs7_verify.c
+++ b/crypto/asymmetric_keys/pkcs7_verify.c
@@ -46,7 +46,8 @@ static int pkcs7_digest(struct pkcs7_message *pkcs7,
return (PTR_ERR(tfm) == -ENOENT) ? -ENOPKG : PTR_ERR(tfm);
desc_size = crypto_shash_descsize(tfm) + sizeof(*desc);
- sinfo->sig.digest_size = digest_size = crypto_shash_digestsize(tfm);
+ sinfo->sig.digest_size = digest_size =
+ ALIGN(crypto_shash_digestsize(tfm), sizeof (*desc));
ret = -ENOMEM;
digest = kzalloc(digest_size + desc_size, GFP_KERNEL);
makes the unaliagned message go away, but I dont know if
sinfo->sig.digest_size needs to be set to the (unaligned) raw
value of crypto_shash_digestsize() itself, and how to verify that
this doesnt break something else in crypto
--Sowmini
next reply other threads:[~2015-10-02 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 14:00 Sowmini Varadhan [this message]
2015-10-08 13:15 ` unaligned access in pkcs7_verify Herbert Xu
2015-10-08 14:43 ` Sowmini Varadhan
2015-10-12 13:32 ` Herbert Xu
2015-10-12 13:46 ` Sowmini Varadhan
2015-10-12 14:06 ` David Miller
2015-10-13 13:39 ` Herbert Xu
2015-10-13 13:29 ` Sowmini Varadhan
2015-10-13 13:36 ` Herbert Xu
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=20151002140014.GI18263@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=dhowells@redhat.com \
--cc=linux-crypto@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).