Re: [PATCH] ipv6: Properly check reference count flag before taking reference

2019-09-25 Thread Eric Dumazet
On 9/23/19 8:06 AM, Petr Vorel wrote: > Hi, > >> People are reporting that WireGuard experiences erratic crashes on 5.3, >> and bisected it down to 7d30a7f6424e. Casually flipping through that >> commit I noticed that a flag is checked using `|` instead of `&`, which in >> this current case,

Re: [PATCH] ipv6: Properly check reference count flag before taking reference

2019-09-23 Thread Jason A. Donenfeld
Apparently even with this (certainly correct) patch attached, users are still experiencing problems. Bug hunting continues, and I'll report back if I figure something out.

Re: [PATCH] ipv6: Properly check reference count flag before taking reference

2019-09-23 Thread Petr Vorel
Hi, > People are reporting that WireGuard experiences erratic crashes on 5.3, > and bisected it down to 7d30a7f6424e. Casually flipping through that > commit I noticed that a flag is checked using `|` instead of `&`, which in > this current case, means that a reference is never incremented, which

[PATCH] ipv6: Properly check reference count flag before taking reference

2019-09-23 Thread Jason A. Donenfeld
People are reporting that WireGuard experiences erratic crashes on 5.3, and bisected it down to 7d30a7f6424e. Casually flipping through that commit I noticed that a flag is checked using `|` instead of `&`, which in this current case, means that a reference is never incremented, which would result