[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20200630.123058.875499975377948138.davem@davemloft.net>
Date: Tue, 30 Jun 2020 12:30:58 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: Jason@...c4.com
Cc: netdev@...r.kernel.org, ndev@...pl.net
Subject: Re: [PATCH net v2 0/8] support AF_PACKET for layer 3 devices
From: "Jason A. Donenfeld" <Jason@...c4.com>
Date: Mon, 29 Jun 2020 19:06:17 -0600
> Hans reported that packets injected by a correct-looking and trivial
> libpcap-based program were not being accepted by wireguard. In
> investigating that, I noticed that a few devices weren't properly
> handling AF_PACKET-injected packets, and so this series introduces a bit
> of shared infrastructure to support that.
...
> This patchset addresses the issue by first adding a layer 3 header parse
> function, much akin to the existing one for layer 2 packets, and then
> adds a shared header_ops structure that, also much akin to the existing
> one for layer 2 packets. Then it wires it up to a few immediate places
> that stuck out as requiring it, and does a bit of cleanup.
>
> This patchset seems like it's fixing real bugs, so it might be
> appropriate for stable. But they're also very old bugs, so if you'd
> rather not backport to stable, that'd make sense to me too.
Series applied, thanks Jason.
I think for now I'll defer on a -stable submission for this work. But
in the future maybe we can reconsider.
Thanks.
Powered by blists - more mailing lists