patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <luca.boccassi@gmail.com>
To: Rahul Bhansali <rbhansali@marvell.com>
Cc: stable@dpdk.org
Subject: Re: [PATCH 22.11] net/cnxk: fix lock for security session ops
Date: Fri, 4 Jul 2025 02:02:20 +0100	[thread overview]
Message-ID: <CAMw=ZnQ6o_G8iwnFAb3oD=rt-2B4MrXp0KAYXoGhQFctqFaRxQ@mail.gmail.com> (raw)
In-Reply-To: <20250703112354.57978-1-rbhansali@marvell.com>

On Thu, 3 Jul 2025 at 12:24, Rahul Bhansali <rbhansali@marvell.com> wrote:
>
> [ upstream commit 9bebc33703df999a405ed7103dc45230d0f1fbda ]
>
> Add fixes to have lock on security session update, write and read to
> prevent corruption.
>
> Fixes: 8efa348e8160 ("net/cnxk: support custom SA index")
>
> Signed-off-by: Rahul Bhansali <rbhansali@marvell.com>
> ---
>  drivers/net/cnxk/cn10k_ethdev_sec.c | 107 +++++++++++++++++++++++-----
>  1 file changed, 90 insertions(+), 17 deletions(-)

Thanks for the backport, but unfortunately it doesn't build, please
double check it:

../drivers/net/cnxk/cn10k_ethdev_sec.c: In function ‘rte_pmd_cnxk_hw_sa_read’:
../drivers/net/cnxk/cn10k_ethdev_sec.c:1013:16: error: ‘inb’
undeclared (first use in this function); did you mean ‘int’?
 1013 |         lock = inb ? &dev->inb.lock : &dev->outb.lock;
      |                ^~~
      |                int
../drivers/net/cnxk/cn10k_ethdev_sec.c:1013:16: note: each undeclared
identifier is reported only once for each function it appears in
../drivers/net/cnxk/cn10k_ethdev_sec.c: In function ‘rte_pmd_cnxk_hw_sa_write’:
../drivers/net/cnxk/cn10k_ethdev_sec.c:1057:16: error: ‘inb’
undeclared (first use in this function); did you mean ‘int’?
 1057 |         lock = inb ? &dev->inb.lock : &dev->outb.lock;
      |                ^~~
      |                int

      reply	other threads:[~2025-07-04  1:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03 11:23 Rahul Bhansali
2025-07-04  1:02 ` Luca Boccassi [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='CAMw=ZnQ6o_G8iwnFAb3oD=rt-2B4MrXp0KAYXoGhQFctqFaRxQ@mail.gmail.com' \
    --to=luca.boccassi@gmail.com \
    --cc=rbhansali@marvell.com \
    --cc=stable@dpdk.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).