wireguard: queueing: do not account for pfmemalloc when clearing skb header
Before8b7008620b
("net: Don't copy pfmemalloc flag in __copy_skb_ header()"), the pfmemalloc flag used to be between headers_start and headers_end, which is a region we clear when preparing the packet for encryption/decryption. This is a parameter we certainly want to preserve, which is why8b7008620b
moved it out of there. The code here was written in a world before8b7008620b
, though, where we had to manually account for it. This commit brings things up to speed. Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
9a69a4c880
commit
04d2ea92a1
|
@ -83,13 +83,10 @@ static inline __be16 wg_skb_examine_untrusted_ip_hdr(struct sk_buff *skb)
|
|||
|
||||
static inline void wg_reset_packet(struct sk_buff *skb)
|
||||
{
|
||||
const int pfmemalloc = skb->pfmemalloc;
|
||||
|
||||
skb_scrub_packet(skb, true);
|
||||
memset(&skb->headers_start, 0,
|
||||
offsetof(struct sk_buff, headers_end) -
|
||||
offsetof(struct sk_buff, headers_start));
|
||||
skb->pfmemalloc = pfmemalloc;
|
||||
skb->queue_mapping = 0;
|
||||
skb->nohdr = 0;
|
||||
skb->peeked = 0;
|
||||
|
|
Loading…
Reference in New Issue