From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
sergey.senozhatsky.work@gmail.com,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: [PATCH] trivial: report backend_cra_name when allocation fails
Date: Wed, 10 Jun 2015 22:27:47 +0900 [thread overview]
Message-ID: <1433942868-16447-1-git-send-email-sergey.senozhatsky@gmail.com> (raw)
Hello,
A trivial patch.
My wifi stopped working recently, and the error message was not too
informative (at least to me):
kernel: wlp2s0: authenticate with 64:e5:99:74:dc:44
kernel: wlp2s0: send auth to 64:e5:99:74:dc:44 (try 1/3)
kernel: wlp2s0: authenticated
kernel: wlp2s0: associate with 64:e5:99:74:dc:44 (try 1/3)
kernel: wlp2s0: RX AssocResp from 64:e5:99:74:dc:44 (capab=0x411 status=0 aid=1)
kernel: wlp2s0: associated
kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
dhclient[355]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67
kernel: DRBG: could not allocate digest TFM handle
kernel: wlp2s0: deauthenticating from 64:e5:99:74:dc:44 by local choice (Reason: 1=UNSPECIFIED)
kernel: cfg80211: Calling CRDA to update world regulatory domain
an update error message
DRBG: could not allocate digest TFM handle: hmac(sha256)
is slightly more helpful (didn't have sha256 config enabled).
Sergey Senozhatsky (1):
crypto/drbg: report backend_cra_name when allocation fails
crypto/drbg.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
--
2.4.3.368.g7974889
next reply other threads:[~2015-06-10 13:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 13:27 Sergey Senozhatsky [this message]
2015-06-10 13:27 ` [PATCH] crypto/drbg: " Sergey Senozhatsky
2015-06-10 15:09 ` Stephan Mueller
2015-06-10 23:38 ` Sergey Senozhatsky
2015-06-11 14:00 ` Herbert Xu
2015-06-11 0:28 ` [PATCH] trivial: " Herbert Xu
2015-06-11 11:09 ` Sergey Senozhatsky
2015-06-11 13:35 ` Stephan Mueller
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=1433942868-16447-1-git-send-email-sergey.senozhatsky@gmail.com \
--to=sergey.senozhatsky@gmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sergey.senozhatsky.work@gmail.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®