linux-kernel - Re: [PATCH 00/10] bpf samples: Uses libbpf in tools/lib to do BPF operations

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 17 Dec 2015 14:51:19 +0800
From:	"Wangnan (F)" <wangnan0@...wei.com>
To:	Daniel Wagner <daniel.wagner@...-carit.de>, <ast@...nel.org>,
	<agartrell@...com>, <acme@...hat.com>, <bblanco@...mgrid.com>,
	<daniel@...earbox.net>, <davem@...emloft.net>, <mingo@...nel.org>,
	<jolsa@...nel.org>, <xiakaixu@...wei.com>,
	<holzheu@...ux.vnet.ibm.com>, <yang.shi@...aro.org>
CC:	<linux-kernel@...r.kernel.org>, <pi3orama@....com>
Subject: Re: [PATCH 00/10] bpf samples: Uses libbpf in tools/lib to do BPF
 operations



On 2015/12/17 14:38, Daniel Wagner wrote:
> Hi,
>
> On 12/17/2015 06:23 AM, Wang Nan wrote:
>> Since we already have libbpf in tools/lib, we don't need to maintain
>> another bpf loader and operations library in samples/bpf.
>>
>> In patchset:
>>
>>   Patch 1/10 - 7/10 improves libbpf, add missing features to support
>>   samples,
>>
>>   Patch 8/10 adds utils.[ch], which creates similar API like old
>>   bpf_load.c and libbpf.c.
>>
>>   Patch 9/10 replace all sampels to use API provides by utils.[ch] and
>>   libbpf.
>>
>>   Patch 10/10 removes unneeded files.
> Which tree did you use for your patches? I tried to apply them against
> mainline and net-next which didn't really work out.

These patches based on Arnaldo's 'perf/core' because of those libbpf
changes.

Which tree is the right one for this? net-next?

Thank you.

> cheers,
> daniel


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/