From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Everest K.C. <everestkc@everestkc.com.np>, <horms@kernel.org>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>
Cc: <netdev@vger.kernel.org>, <kernel-janitors@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <steffen.klassert@secunet.com>,
<herbert@gondor.apana.org.au>
Subject: Re: [PATCH][next] xfrm: Add error handling when nla_put_u32() returns an error
Date: Wed, 13 Nov 2024 15:12:02 +0100 [thread overview]
Message-ID: <2092f824-b60e-4d78-991b-61b35a312597@intel.com> (raw)
In-Reply-To: <20241112233613.6444-1-everestkc@everestkc.com.np>
On 11/13/24 00:36, Everest K.C. wrote:
> Error handling is missing when call to nla_put_u32() fails.
> Handle the error when the call to nla_put_u32() returns an error.
>
> The error was reported by Coverity Scan.
> Report:
> CID 1601525: (#1 of 1): Unused value (UNUSED_VALUE)
> returned_value: Assigning value from nla_put_u32(skb, XFRMA_SA_PCPU, x->pcpu_num)
> to err here, but that stored value is overwritten before it can be used
>
> Fixes: 1ddf9916ac09 ("xfrm: Add support for per cpu xfrm state handling.")
> Signed-off-by: Everest K.C. <everestkc@everestkc.com.np>
> ---
> net/xfrm/xfrm_user.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/net/xfrm/xfrm_user.c b/net/xfrm/xfrm_user.c
> index f0ee0c7a59dd..a784598cc7cf 100644
> --- a/net/xfrm/xfrm_user.c
> +++ b/net/xfrm/xfrm_user.c
> @@ -2607,9 +2607,12 @@ static int build_aevent(struct sk_buff *skb, struct xfrm_state *x, const struct
> err = xfrm_if_id_put(skb, x->if_id);
> if (err)
> goto out_cancel;
> - if (x->pcpu_num != UINT_MAX)
> + if (x->pcpu_num != UINT_MAX) {
> err = nla_put_u32(skb, XFRMA_SA_PCPU, x->pcpu_num);
> -
> + if (err)
> + goto out_cancel;
> + }
> +
> if (x->dir) {
> err = nla_put_u8(skb, XFRMA_SA_DIR, x->dir);
> if (err)
this is a fix indeed,
Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
--
I find nla_put*() familiy error handling very ugly for the calling code,
especially given that some of the calls are conditional
I would like to refactor it some day, to give the caller possibility to
just put all the needed fields and check the error once at the end.
Nesting complicates things a bit, but perhaps it could be also covered
in such way (didn't checked yet).
prev parent reply other threads:[~2024-11-13 14:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 23:36 Everest K.C.
2024-11-13 10:59 ` Simon Horman
2024-11-13 13:10 ` Dan Carpenter
2024-11-13 14:06 ` Dan Carpenter
2024-11-13 17:59 ` Simon Horman
2024-11-14 19:27 ` Everest K.C.
2024-11-15 8:07 ` Steffen Klassert
2024-11-13 14:12 ` Przemek Kitszel [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=2092f824-b60e-4d78-991b-61b35a312597@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=everestkc@everestkc.com.np \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.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®