Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: msekleta@redhat.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3] net: introduce SO_BPF_EXTENSIONS
Date: Sat, 18 Jan 2014 19:09:16 -0800 (PST)	[thread overview]
Message-ID: <20140118.190916.636296905840181243.davem@davemloft.net> (raw)
In-Reply-To: <1389974985-21160-1-git-send-email-msekleta@redhat.com>

From: Michal Sekletar <msekleta@redhat.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@redhat.com>
> Cc: David Miller <davem@davemloft.net>
> Reviewed-by: Daniel Borkmann <dborkman@redhat.com>

Applied, thanks.

      reply	other threads:[~2014-01-19  3:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17 16:09 [PATCH net-next v3] net: introduce SO_BPF_EXTENSIONS Michal Sekletar
2014-01-19  3:09 ` David Miller [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140118.190916.636296905840181243.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=msekleta@redhat.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox