From: Jakub Kicinski <kuba@kernel.org>
To: Antonio Quartulli <antonio@openvpn.net>
Cc: netdev@vger.kernel.org, edumazet@google.com, sd@queasysnail.net,
davem@davemloft.net, pabeni@redhat.com, ralf@mandelbit.com,
andrew+netdev@lunn.ch, horms@kernel.org, shuah@kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net 2/3] ovpn: ensure packet delivery happens with BH disabled
Date: Wed, 6 May 2026 16:11:35 -0700 [thread overview]
Message-ID: <20260506161135.1db08c2d@kernel.org> (raw)
In-Reply-To: <9ffc1db1-3b67-453e-ae43-e986fdad3694@openvpn.net>
On Wed, 6 May 2026 11:00:20 +0200 Antonio Quartulli wrote:
> > ovpn_decrypt_post() {
> > ...
> > if (unlikely(ret < 0))
> > goto drop;
> > ...
> > drop:
> > if (unlikely(skb))
> > dev_dstats_rx_dropped(peer->ovpn->dev);
> > ...
> > }
> >
> > Since dev_dstats_rx_dropped() updates the same per-CPU dstats structure
> > without disabling bottom halves, could it still be vulnerable to softirq
> > preemption and stat corruption?
> >
>
> Actually we were already looking into this.
> However, since this needs a separate analysis, I wanted to get this
> fixed in a follow up patch.
>
> Would it be ok to pull this PR as is, so we don't hold back the
> outstanding fixes?
>
> Then we will address the issue highlighted by Sashiko in a new patch.
> The problem is similar, but may need to be fixed differently.
Ugh, fair. The way the AI formatted the output made me think
it's an error path in the same function, which would make sense
to address with a single patch.. Pulling now.
prev parent reply other threads:[~2026-05-06 23:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260504230305.2681646-3-antonio@openvpn.net>
2026-05-06 1:00 ` [PATCH net 2/3] ovpn: ensure packet delivery happens with BH disabled Jakub Kicinski
2026-05-06 9:00 ` Antonio Quartulli
2026-05-06 23:11 ` Jakub Kicinski [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=20260506161135.1db08c2d@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=antonio@openvpn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ralf@mandelbit.com \
--cc=sd@queasysnail.net \
--cc=shuah@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