| 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
| ||
|
Date: Sat, 18 Jan 2014 19:09:16 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: msekleta@...hat.com
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH net-next v3] net: introduce SO_BPF_EXTENSIONS
From: Michal Sekletar <msekleta@...hat.com>
Date: Fri, 17 Jan 2014 17:09:45 +0100
> For user space packet capturing libraries such as libpcap, there's
> currently only one way to check which BPF extensions are supported
> by the kernel, that is, commit aa1113d9f85d ("net: filter: return
> -EINVAL if BPF_S_ANC* operation is not supported"). For querying all
> extensions at once this might be rather inconvenient.
>
> Therefore, this patch introduces a new option which can be used as
> an argument for getsockopt(), and allows one to obtain information
> about which BPF extensions are supported by the current kernel.
>
> As David Miller suggests, we do not need to define any bits right
> now and status quo can just return 0 in order to state that this
> versions supports SKF_AD_PROTOCOL up to SKF_AD_PAY_OFFSET. Later
> additions to BPF extensions need to add their bits to the
> bpf_tell_extensions() function, as documented in the comment.
>
> Signed-off-by: Michal Sekletar <msekleta@...hat.com>
> Cc: David Miller <davem@...emloft.net>
> Reviewed-by: Daniel Borkmann <dborkman@...hat.com>
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists