Florian Obser writes:
> On 2022-07-12 14:35 +02, Florian Obser wrote:
>> When the autoconf flag flaps around we might end up with multiple bpf
>> FDs in flight. Things then get confusing. The kernel tells us we can
>> read from the bpf FD but the data is actually "on the other FD", so
>>
On Thu, Jul 14, 2022 at 08:20:41AM +0200, Florian Obser wrote:
| On 2022-07-12 14:35 +02, Florian Obser wrote:
| > When the autoconf flag flaps around we might end up with multiple bpf
| > FDs in flight. Things then get confusing. The kernel tells us we can
| > read from the bpf FD but the data
On 2022-07-12 14:35 +02, Florian Obser wrote:
> When the autoconf flag flaps around we might end up with multiple bpf
> FDs in flight. Things then get confusing. The kernel tells us we can
> read from the bpf FD but the data is actually "on the other FD", so
> read(2) returns 0.
>
> Found the
When the autoconf flag flaps around we might end up with multiple bpf
FDs in flight. Things then get confusing. The kernel tells us we can
read from the bpf FD but the data is actually "on the other FD", so
read(2) returns 0.
Found the hard way by, and patiently debugged with weerd@
One way to
