public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: <edward.cree@amd•com>
Cc: linux-net-drivers@amd•com, davem@davemloft•net, kuba@kernel•org,
	edumazet@google•com, pabeni@redhat•com, ecree.xilinx@gmail•com,
	netdev@vger•kernel.org, habetsm.xilinx@gmail•com,
	dan.carpenter@linaro•org
Subject: Re: [PATCH net] sfc: handle error pointers returned by rhashtable_lookup_get_insert_fast()
Date: Thu, 21 Sep 2023 08:50:22 +0000	[thread overview]
Message-ID: <169528622237.20950.7146192705850531950.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230919183949.59392-1-edward.cree@amd.com>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat•com>:

On Tue, 19 Sep 2023 19:39:49 +0100 you wrote:
> From: Edward Cree <ecree.xilinx@gmail•com>
> 
> Several places in TC offload code assumed that the return from
>  rhashtable_lookup_get_insert_fast() was always either NULL or a valid
>  pointer to an existing entry, but in fact that function can return an
>  error pointer.  In that case, perform the usual cleanup of the newly
>  created entry, then pass up the error, rather than attempting to take a
>  reference on the old entry.
> 
> [...]

Here is the summary with links:
  - [net] sfc: handle error pointers returned by rhashtable_lookup_get_insert_fast()
    https://git.kernel.org/netdev/net/c/fc21f08375db

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2023-09-21  8:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19 18:39 [PATCH net] sfc: handle error pointers returned by rhashtable_lookup_get_insert_fast() edward.cree
2023-09-21  8:50 ` patchwork-bot+netdevbpf [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=169528622237.20950.7146192705850531950.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=dan.carpenter@linaro$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=ecree.xilinx@gmail$(echo .)com \
    --cc=edumazet@google$(echo .)com \
    --cc=edward.cree@amd$(echo .)com \
    --cc=habetsm.xilinx@gmail$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=linux-net-drivers@amd$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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