From: Greg KH <gregkh@linuxfoundation.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
stable@vger.kernel.org, netdev@vger.kernel.org, kuba@kernel.org
Subject: Re: [PATCH stable v5.15,v6.1] Revert "wireguard: device: enable threaded NAPI"
Date: Tue, 17 Feb 2026 11:33:44 +0100 [thread overview]
Message-ID: <2026021715-confetti-endanger-21eb@gregkh> (raw)
In-Reply-To: <CAHmME9rsvaargjbZO8SkswOToUATuWpkQDVykEUty-kWPyu7gA@mail.gmail.com>
On Mon, Feb 16, 2026 at 10:33:53PM +0100, Jason A. Donenfeld wrote:
> On Mon, Feb 16, 2026 at 10:31 PM Daniel Borkmann <daniel@iogearbox.net> wrote:
> > Technically, the backport of commit db9ae3b6b43c ("wireguard: device:
> > enable threaded NAPI") to stable should not have happened since it is
> > more of an optimization rather than a pure fix and addresses a NAPI
> > situation with utilizing many WireGuard tunnel devices in parallel.
>
> Indeed.
>
> > Revert it from stable given the backport triggers a regression for
> > mentioned kernels.
>
> Thanks.
>
> Acked-by: Jason A. Donenfeld <Jason@zx2c4.com>
>
> If that helps with Greg queueing this up.
I'll go queue it up now, thanks for the revert. But it's ok being in
the 6.6.y and 6.12.y and newer kernels, right?
thanks,
greg k-h
next prev parent reply other threads:[~2026-02-17 10:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 21:31 [PATCH stable v5.15,v6.1] Revert "wireguard: device: enable threaded NAPI" Daniel Borkmann
2026-02-16 21:33 ` Jason A. Donenfeld
2026-02-17 10:33 ` Greg KH [this message]
2026-02-17 11:01 ` Daniel Borkmann
2026-02-17 11:25 ` Greg KH
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=2026021715-confetti-endanger-21eb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Jason@zx2c4.com \
--cc=daniel@iogearbox.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.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