All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Antonio Quartulli <antonio@openvpn.net>
Cc: Xin Long <lucien.xin@gmail.com>,
	davem@davemloft.net, Jakub Kicinski <kuba@kernel.org>,
	network dev <netdev@vger.kernel.org>,
	Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCHv5 net-next 1/2] udp: call udp_encap_enable for v6 sockets when enabling encap
Date: Sat, 2 Apr 2022 13:28:45 +0200	[thread overview]
Message-ID: <YkgzbTKdmAekAq6p@kroah.com> (raw)
In-Reply-To: <e5553cba-c29d-0a22-c362-0ce1e1ef4b41@openvpn.net>

On Thu, Mar 31, 2022 at 03:06:41PM +0200, Antonio Quartulli wrote:
> Hi,
> 
> On 29/03/2022 15:30, Greg Kroah-Hartman wrote:
> > > I would like to propose to take this patch in stable releases.
> > > Greg, is this an option?
> > > 
> > > Commit in the linux kernel is:
> > > a4a600dd301ccde6ea239804ec1f19364a39d643
> > 
> > 
> > What stable tree(s) should this apply to, and where have you tested it?
> 
> Sorry for the delay, Greg, but I wanted to run some extra tests on the
> various longterm kernel releases.
> 
> This bug exists since "ever", therefore ideally it could/should be applied
> to all stable trees.
> 
> However, this patch applies as-is only to v5.10 and v5.4 (you need to ignore
> the hunk for 'drivers/net/bareudp.c' on the latter).
> 
> Older trees require a different code change.
> 
> My tests on v5.10 and v5.4 show that the patch works as expected.
> 
> Therefore, could it be backported to these 2 trees?
> It can get my
> 
> Tested-by: Antonio Quartulli <antonio@openvpn.net>

Now queued up, thanks.

greg k-h

  reply	other threads:[~2022-04-02 11:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03  8:54 [PATCHv5 net-next 0/2] net: enable udp v6 sockets receiving v4 packets with UDP Xin Long
2021-02-03  8:54 ` [PATCHv5 net-next 1/2] udp: call udp_encap_enable for v6 sockets when enabling encap Xin Long
2021-02-03  8:54   ` [PATCHv5 net-next 2/2] rxrpc: call udp_tunnel_encap_enable in rxrpc_open_socket Xin Long
2021-02-03  9:50   ` David Howells
2022-03-29 13:24   ` [PATCHv5 net-next 1/2] udp: call udp_encap_enable for v6 sockets when enabling encap Antonio Quartulli
2022-03-29 13:30     ` Greg Kroah-Hartman
2022-03-31 13:06       ` Antonio Quartulli
2022-04-02 11:28         ` Greg Kroah-Hartman [this message]
2021-02-05  3:00 ` [PATCHv5 net-next 0/2] net: enable udp v6 sockets receiving v4 packets with UDP patchwork-bot+netdevbpf

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=YkgzbTKdmAekAq6p@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=antonio@openvpn.net \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=willemb@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.