From: Joe Damato <jdamato@fastly.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, edumazet@google.com,
amritha.nambiar@intel.com, sridhar.samudrala@intel.com,
mkarsten@uwaterloo.ca, "David S. Miller" <davem@davemloft.net>,
open list <linux-kernel@vger.kernel.org>,
Mina Almasry <almasrymina@google.com>,
Simon Horman <horms@kernel.org>
Subject: Re: [net v2 0/2] Fix rcu_read_lock issues in netdev-genl
Date: Wed, 13 Nov 2024 22:29:50 -0800 [thread overview]
Message-ID: <ZzWY3iAbgWEDcQzV@LQ3V64L9R2> (raw)
In-Reply-To: <20241113184735.28416e41@kernel.org>
On Wed, Nov 13, 2024 at 06:47:35PM -0800, Jakub Kicinski wrote:
> On Wed, 13 Nov 2024 02:17:50 +0000 Joe Damato wrote:
> > base-commit: a58f00ed24b849d449f7134fd5d86f07090fe2f5
>
> which is a net-next commit.. please rebase on net
I thought I asked about this in the previous thread, but I probably
wasn't clear with my question.
Let me try again:
Patch 1 will apply to net and is a fixes and CC's stable, and fixes
a similar issue to the one Paolo reported, not the exact same path,
though.
Patch 2 will not apply to net, because the code it fixes is not in
net yet. This fixes the splat Paolo reported.
So... back to the question in the cover letter from the RFC :) I
suppose the right thing to do is split the series:
- Rebase patch 1 on net (it applies as is) and send it on its own
- Send patch 2 on its own against net-next
Or... something else ?
next prev parent reply other threads:[~2024-11-14 6:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 2:17 [net v2 0/2] Fix rcu_read_lock issues in netdev-genl Joe Damato
2024-11-13 2:17 ` [net v2 1/2] netdev-genl: Hold rcu_read_lock in napi_get Joe Damato
2024-11-13 2:17 ` [net v2 2/2] netdev-genl: Hold rcu_read_lock in napi_set Joe Damato
2024-11-14 2:47 ` [net v2 0/2] Fix rcu_read_lock issues in netdev-genl Jakub Kicinski
2024-11-14 6:29 ` Joe Damato [this message]
2024-11-14 9:06 ` Paolo Abeni
2024-11-14 17:58 ` Joe Damato
2024-11-14 18:32 ` Paolo Abeni
2024-11-14 19:31 ` Jakub Kicinski
2024-11-14 20:13 ` Joe Damato
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=ZzWY3iAbgWEDcQzV@LQ3V64L9R2 \
--to=jdamato@fastly.com \
--cc=almasrymina@google.com \
--cc=amritha.nambiar@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkarsten@uwaterloo.ca \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sridhar.samudrala@intel.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;
as well as URLs for NNTP newsgroup(s).