public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Roman Gushchin <roman.gushchin@linux.dev>
To: Antonio Quartulli <antonio@openvpn.net>
Cc: Jakub Kicinski <kuba@kernel.org>,
	 netdev@vger.kernel.org, ralf@mandelbit.com,
	 Hyunwoo Kim <imv4bel@gmail.com>,
	 Sabrina Dubroca <sd@queasysnail.net>
Subject: Re: [RFC net] ovpn: fix race between deleting interface and adding new peer
Date: Tue, 05 May 2026 08:07:56 +0000	[thread overview]
Message-ID: <7ia4qznq1dpf.fsf@castle.c.googlers.com> (raw)
In-Reply-To: <33639813-1de3-4a82-966f-7a0daab25433@openvpn.net> (Antonio Quartulli's message of "Tue, 5 May 2026 02:04:14 +0200")

Antonio Quartulli <antonio@openvpn.net> writes:

> On 05/05/2026 01:54, Jakub Kicinski wrote:
>> On Mon,  4 May 2026 16:20:33 +0200 Antonio Quartulli wrote:
>>> This patch is sent as RFC to give the AI a chance to review it once
>>> again, since it was able to spot a new race condition in its
>>> previous version.
>> FWIW I think you can just ask for Sashiko to track the openvpn
>> mailing
>> list?
>
> Yes, indeed.
> I just went through this discussion for the batman-adv kernel module.
>
> @Roman: is it possible for Sashiko to consider certain patches only?
> On the openvpn-devel mailing list there are also patches for the
> openvpn userspace program flying around.

Sashiko ignores all patches which it can't apply successfully to the
kernel tree, so it's likely not a problem.

If it will be a problem, I'll master something.

Thanks

>
>
> Regards,

  reply	other threads:[~2026-05-05  8:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-04 14:20 [RFC net] ovpn: fix race between deleting interface and adding new peer Antonio Quartulli
2026-05-04 23:54 ` Jakub Kicinski
2026-05-05  0:04   ` Antonio Quartulli
2026-05-05  8:07     ` Roman Gushchin [this message]
2026-05-05 19:20 ` Antonio Quartulli

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=7ia4qznq1dpf.fsf@castle.c.googlers.com \
    --to=roman.gushchin@linux.dev \
    --cc=antonio@openvpn.net \
    --cc=imv4bel@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ralf@mandelbit.com \
    --cc=sd@queasysnail.net \
    /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