netdev - RE: [PATCH bpf-next v3 02/10] xsk: add TX timestamp and TX checksum offload support

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]

Message-ID: <PH0PR11MB5830AA76FE2D8E03CF66E265D8CAA@PH0PR11MB5830.namprd11.prod.outlook.com>
Date: Thu, 5 Oct 2023 01:16:30 +0000
From: "Song, Yoong Siang" <yoong.siang.song@...el.com>
To: Stanislav Fomichev <sdf@...gle.com>
CC: "bpf@...r.kernel.org" <bpf@...r.kernel.org>, "ast@...nel.org"
	<ast@...nel.org>, "daniel@...earbox.net" <daniel@...earbox.net>,
	"andrii@...nel.org" <andrii@...nel.org>, "martin.lau@...ux.dev"
	<martin.lau@...ux.dev>, "song@...nel.org" <song@...nel.org>, "yhs@...com"
	<yhs@...com>, "john.fastabend@...il.com" <john.fastabend@...il.com>,
	"kpsingh@...nel.org" <kpsingh@...nel.org>, "haoluo@...gle.com"
	<haoluo@...gle.com>, "jolsa@...nel.org" <jolsa@...nel.org>, "kuba@...nel.org"
	<kuba@...nel.org>, "toke@...nel.org" <toke@...nel.org>, "willemb@...gle.com"
	<willemb@...gle.com>, "dsahern@...nel.org" <dsahern@...nel.org>, "Karlsson,
 Magnus" <magnus.karlsson@...el.com>, "bjorn@...nel.org" <bjorn@...nel.org>,
	"Fijalkowski, Maciej" <maciej.fijalkowski@...el.com>, "hawk@...nel.org"
	<hawk@...nel.org>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"xdp-hints@...-project.net" <xdp-hints@...-project.net>
Subject: RE: [PATCH bpf-next v3 02/10] xsk: add TX timestamp and TX checksum
 offload support

On Thursday, October 5, 2023 1:57 AM Stanislav Fomichev <sdf@...gle.com> wrote:
>Yeah, looks like this part is not happy, doesn't look like BIT() is exported to UAPI,
>per:
>
>check for #defines like: 1 << <digit> that could be BIT(digit), it is not exported to
>uapi
Noted.
>
>So I'll revert to << like in the rest of this file.
Sure. I am ok to keep <<