From: clabbe.montjoie@gmail.com (Corentin LABBE)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] crypto: sunxi - don't print confusing data
Date: Wed, 27 Jan 2016 20:42:26 +0100 [thread overview]
Message-ID: <56A91DA2.5040608@gmail.com> (raw)
In-Reply-To: <1453815902-3070323-1-git-send-email-arnd@arndb.de>
Le 26/01/2016 14:44, Arnd Bergmann a ?crit :
> gcc correctly warns that the printk output contains a variable that
> it thinks is not initialized in some cases:
>
> drivers/crypto/sunxi-ss/sun4i-ss-cipher.c: In function 'sun4i_ss_cipher_poll':
> drivers/crypto/sunxi-ss/sun4i-ss-cipher.c:254:76: warning: 'todo' may be used uninitialized in this function [-Wmaybe-uninitialized]
> drivers/crypto/sunxi-ss/sun4i-ss-cipher.c:144:15: note: 'todo' was declared here
>
> A closer look at the function reveals that the variable is always
> initialized at this point (ileft is guaranteed to be positive at the
> start), but its contents are not well-defined:
> Depending on some other variables, it might be either a count in
> words or bytes, and it could refer to either input or output.
>
> The easiest solution apparently is to remove the confusing output
> and let the reader figure out the state from the other variables.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> drivers/crypto/sunxi-ss/sun4i-ss-cipher.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/crypto/sunxi-ss/sun4i-ss-cipher.c b/drivers/crypto/sunxi-ss/sun4i-ss-cipher.c
> index a19ee127edca..7be3fbcd8d78 100644
> --- a/drivers/crypto/sunxi-ss/sun4i-ss-cipher.c
> +++ b/drivers/crypto/sunxi-ss/sun4i-ss-cipher.c
> @@ -251,11 +251,10 @@ static int sun4i_ss_cipher_poll(struct ablkcipher_request *areq)
> spaces = readl(ss->base + SS_FCSR);
> rx_cnt = SS_RXFIFO_SPACES(spaces);
> tx_cnt = SS_TXFIFO_SPACES(spaces);
> - dev_dbg(ss->dev, "%x %u/%u %u/%u cnt=%u %u/%u %u/%u cnt=%u %u %u\n",
> + dev_dbg(ss->dev, "%x %u/%u %u/%u cnt=%u %u/%u %u/%u cnt=%u %u\n",
> mode,
> oi, mi.length, ileft, areq->nbytes, rx_cnt,
> - oo, mo.length, oleft, areq->nbytes, tx_cnt,
> - todo, ob);
> + oo, mo.length, oleft, areq->nbytes, tx_cnt, ob);
>
> if (tx_cnt == 0)
> continue;
>
Hello
A bit late but Acked-by: LABBE Corentin <clabbe.montjoie@gmail.com>
Thanks
prev parent reply other threads:[~2016-01-27 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 13:44 [PATCH v2 1/2] crypto: sunxi - don't print confusing data Arnd Bergmann
2016-01-26 13:47 ` [PATCH v2 2/2] crypto: jitterentropy - always select CRYPTO_RNG Arnd Bergmann
2016-01-27 14:17 ` Herbert Xu
2016-01-27 14:17 ` [PATCH v2 1/2] crypto: sunxi - don't print confusing data Herbert Xu
2016-01-27 19:42 ` Corentin LABBE [this message]
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=56A91DA2.5040608@gmail.com \
--to=clabbe.montjoie@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).