netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: Kees Bakker <kees@ijzerbout.nl>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH 1/4] xfrm: Add support for per cpu xfrm state handling.
Date: Tue, 12 Nov 2024 12:03:25 +0100	[thread overview]
Message-ID: <ZzM1/S72Qj0tBCC0@gauss3.secunet.de> (raw)
In-Reply-To: <f9eb1025-9a3d-42b3-a3e4-990a0fadbeaf@ijzerbout.nl>

On Mon, Nov 11, 2024 at 09:42:02PM +0100, Kees Bakker wrote:
> Hi Steffen,
> 
> Sorry for the direct email. Did you perhaps forgot a "goto out_cancel" here?

Yes, looks like that. Do you want to send a patch?

> 
> diff --git a/net/xfrm/xfrm_user.c b/net/xfrm/xfrm_user.c
> [...]
> @@ -2576,6 +2603,8 @@ 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)
> +        err = nla_put_u32(skb, XFRMA_SA_PCPU, x->pcpu_num);
> 
>      if (x->dir) {
>          err = nla_put_u8(skb, XFRMA_SA_DIR, x->dir);
> 
> -- 
> Kees Bakker

  reply	other threads:[~2024-11-12 11:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-11 20:42 [PATCH 1/4] xfrm: Add support for per cpu xfrm state handling Kees Bakker
2024-11-12 11:03 ` Steffen Klassert [this message]
2024-11-12 19:21   ` Kees Bakker
2024-11-14 10:59     ` Steffen Klassert
  -- strict thread matches above, loose matches on Subject: below --
2024-10-07  6:44 [PATCH 0/4] xfrm: Add support for RFC 9611 per cpu xfrm states Steffen Klassert
2024-10-07  6:44 ` [PATCH 1/4] xfrm: Add support for per cpu xfrm state handling Steffen Klassert
2024-10-08 16:47   ` Simon Horman
2024-10-11  8:22     ` Steffen Klassert
2024-10-10 18:22   ` kernel test robot

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=ZzM1/S72Qj0tBCC0@gauss3.secunet.de \
    --to=steffen.klassert@secunet.com \
    --cc=kees@ijzerbout.nl \
    --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).