On 09/28/2017 07:33 PM, Craig Gallek wrote:
On Wed, Sep 27, 2017 at 6:03 PM, Daniel Borkmann wrote:
On 09/27/2017 06:29 PM, Alexei Starovoitov wrote:
On 9/27/17 7:04 AM, Craig Gallek wrote:
From: Craig Gallek
[...]
yes it will break loading of pre-compiled .o
Instead of breaking, let's fi
On Wed, Sep 27, 2017 at 6:03 PM, Daniel Borkmann wrote:
> On 09/27/2017 06:29 PM, Alexei Starovoitov wrote:
>>
>> On 9/27/17 7:04 AM, Craig Gallek wrote:
>>>
>>> From: Craig Gallek
>>>
>>> This extends struct bpf_map_def to include a flags field. Note that
>>> this has the potential to break the
On 09/27/2017 06:29 PM, Alexei Starovoitov wrote:
On 9/27/17 7:04 AM, Craig Gallek wrote:
From: Craig Gallek
This extends struct bpf_map_def to include a flags field. Note that
this has the potential to break the validation logic in
bpf_object__validate_maps and bpf_object__init_maps as they
On 9/27/17 7:04 AM, Craig Gallek wrote:
From: Craig Gallek
This extends struct bpf_map_def to include a flags field. Note that
this has the potential to break the validation logic in
bpf_object__validate_maps and bpf_object__init_maps as they use
sizeof(struct bpf_map_def) as a minimal allowab
From: Craig Gallek
This extends struct bpf_map_def to include a flags field. Note that
this has the potential to break the validation logic in
bpf_object__validate_maps and bpf_object__init_maps as they use
sizeof(struct bpf_map_def) as a minimal allowable size of a map section.
Any bpf program