From: Leon Romanovsky <leon@kernel.org>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Cc: dhowells@redhat.com, davem@davemloft.net, kuba@kernel.org,
linux-afs@lists.infradead.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rxrpc: rxkad: replace if (cond) BUG() with BUG_ON()
Date: Thu, 18 Mar 2021 10:14:20 +0200 [thread overview]
Message-ID: <YFML3Dqpyc4Gcg2U@unreal> (raw)
In-Reply-To: <1615952318-4861-1-git-send-email-jiapeng.chong@linux.alibaba.com>
On Wed, Mar 17, 2021 at 11:38:38AM +0800, Jiapeng Chong wrote:
> Fix the following coccicheck warnings:
>
> ./net/rxrpc/rxkad.c:1140:2-5: WARNING: Use BUG_ON instead of if
> condition followed by BUG.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
> ---
> net/rxrpc/rxkad.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/net/rxrpc/rxkad.c b/net/rxrpc/rxkad.c
> index e2e9e9b..bfa3d9a 100644
> --- a/net/rxrpc/rxkad.c
> +++ b/net/rxrpc/rxkad.c
> @@ -1135,9 +1135,8 @@ static void rxkad_decrypt_response(struct rxrpc_connection *conn,
> ntohl(session_key->n[0]), ntohl(session_key->n[1]));
>
> mutex_lock(&rxkad_ci_mutex);
> - if (crypto_sync_skcipher_setkey(rxkad_ci, session_key->x,
> - sizeof(*session_key)) < 0)
> - BUG();
> + BUG_ON(crypto_sync_skcipher_setkey(rxkad_ci, session_key->x,
> + sizeof(*session_key)) < 0);
It will be better to delete this BUG_ON() or find a way to ensure
that it doesn't happen and delete after that.
Thanks
>
> memcpy(&iv, session_key, sizeof(iv));
>
> --
> 1.8.3.1
>
prev parent reply other threads:[~2021-03-18 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 3:38 [PATCH] rxrpc: rxkad: replace if (cond) BUG() with BUG_ON() Jiapeng Chong
2021-03-18 8:14 ` Leon Romanovsky [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=YFML3Dqpyc4Gcg2U@unreal \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=kuba@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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).