public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Eric Dumazet <eric.dumazet@gmail•com>
Cc: davem@davemloft•net, kuba@kernel•org, pabeni@redhat•com,
	netdev@vger•kernel.org, edumazet@google•com
Subject: Re: [PATCH v2 net-next 0/2] raw: RCU conversion
Date: Sun, 19 Jun 2022 09:10:12 +0000	[thread overview]
Message-ID: <165562981269.6554.17099795352757698507.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220618034705.2809237-1-eric.dumazet@gmail.com>

Hello:

This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft•net>:

On Fri, 17 Jun 2022 20:47:03 -0700 you wrote:
> From: Eric Dumazet <edumazet@google•com>
> 
> Using rwlock in networking code is extremely risky.
> writers can starve if enough readers are constantly
> grabing the rwlock.
> 
> I thought rwlock were at fault and sent this patch:
> 
> [...]

Here is the summary with links:
  - [v2,net-next,1/2] raw: use more conventional iterators
    (no matching commit)
  - [v2,net-next,2/2] raw: convert raw sockets to RCU
    https://git.kernel.org/netdev/net-next/c/0daf07e52709

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



      parent reply	other threads:[~2022-06-19  9:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-18  3:47 [PATCH v2 net-next 0/2] raw: RCU conversion Eric Dumazet
2022-06-18  3:47 ` [PATCH v2 net-next 1/2] raw: use more conventional iterators Eric Dumazet
2022-06-18  3:47 ` [PATCH v2 net-next 2/2] raw: convert raw sockets to RCU Eric Dumazet
2022-06-19  9:10 ` 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=165562981269.6554.17099795352757698507.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=eric.dumazet@gmail$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --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