Re: [PATCH bpf 1/2] libbpf: fix invalid munmap call

2019-05-06 Thread Daniel Borkmann
On 05/06/2019 10:40 AM, Björn Töpel wrote: > On Mon, 6 May 2019 at 10:26, Daniel Borkmann wrote: >> On 04/30/2019 02:45 PM, Björn Töpel wrote: >>> From: Björn Töpel >>> >>> When unmapping the AF_XDP memory regions used for the rings, an >>> invalid address was passed to the munmap() calls. Instea

Re: [PATCH bpf 1/2] libbpf: fix invalid munmap call

2019-05-06 Thread Björn Töpel
On Mon, 6 May 2019 at 10:26, Daniel Borkmann wrote: > > On 04/30/2019 02:45 PM, Björn Töpel wrote: > > From: Björn Töpel > > > > When unmapping the AF_XDP memory regions used for the rings, an > > invalid address was passed to the munmap() calls. Instead of passing > > the beginning of the memory

Re: [PATCH bpf 1/2] libbpf: fix invalid munmap call

2019-05-06 Thread Daniel Borkmann
On 04/30/2019 02:45 PM, Björn Töpel wrote: > From: Björn Töpel > > When unmapping the AF_XDP memory regions used for the rings, an > invalid address was passed to the munmap() calls. Instead of passing > the beginning of the memory region, the descriptor region was passed > to munmap. > > When t

Re: [PATCH bpf 1/2] libbpf: fix invalid munmap call

2019-04-30 Thread William Tu
On Tue, Apr 30, 2019 at 5:46 AM Björn Töpel wrote: > > From: Björn Töpel > > When unmapping the AF_XDP memory regions used for the rings, an > invalid address was passed to the munmap() calls. Instead of passing > the beginning of the memory region, the descriptor region was passed > to munmap. >

[PATCH bpf 1/2] libbpf: fix invalid munmap call

2019-04-30 Thread Björn Töpel
From: Björn Töpel When unmapping the AF_XDP memory regions used for the rings, an invalid address was passed to the munmap() calls. Instead of passing the beginning of the memory region, the descriptor region was passed to munmap. When the userspace application tried to tear down an AF_XDP socke