From: John Fastabend <john.fastabend@gmail.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: alexei.starovoitov@gmail.com, daniel@iogearbox.net,
davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [net PATCH] bpf: remove SK_REDIRECT from UAPI
Date: Wed, 1 Nov 2017 06:50:29 -0700 [thread overview]
Message-ID: <c76037b1-cc56-5f1f-5893-2b00d4c895f7@gmail.com> (raw)
In-Reply-To: <20171101082621.GC1977@nanopsycho.orion>
On 11/01/2017 01:26 AM, Jiri Pirko wrote:
> Wed, Nov 01, 2017 at 03:17:31AM CET, john.fastabend@gmail.com wrote:
>> Now that SK_REDIRECT is no longer a valid return code. Remove it
>>from the UAPI completely. Then do a namespace remapping internal
>> to sockmap so SK_REDIRECT is no longer externally visible.
>>
>> Patchs primary change is to do a namechange from SK_REDIRECT to
>> __SK_REDIRECT
>>
>> Reported-by: Alexei Starovoitov <ast@kernel.org>
>> Signed-off-by: John Fastabend <john.fastabend@gmail.com>
>> ---
>> include/uapi/linux/bpf.h | 1 -
>> kernel/bpf/sockmap.c | 16 ++++++++++++----
>> tools/include/uapi/linux/bpf.h | 3 +--
>> 3 files changed, 13 insertions(+), 7 deletions(-)
>>
>> diff --git a/include/uapi/linux/bpf.h b/include/uapi/linux/bpf.h
>> index 0d7948c..7bf4c75 100644
>> --- a/include/uapi/linux/bpf.h
>> +++ b/include/uapi/linux/bpf.h
>> @@ -788,7 +788,6 @@ struct xdp_md {
>> enum sk_action {
>> SK_DROP = 0,
>> SK_PASS,
>> - SK_REDIRECT,
>
> Is it really ok to do uapi changes like this?
>
sockmap feature was only added in net so there is no released kernel
with SK_REDIRECT. And there is no user facing code that can interpret
the SK_REDIRECT return code it is only helpful for interface internals.
So best to remove it rather than have it enshrined in UAPI
unnecessarily.
.John
next prev parent reply other threads:[~2017-11-01 13:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 2:17 [net PATCH] bpf: remove SK_REDIRECT from UAPI John Fastabend
2017-11-01 2:44 ` David Miller
2017-11-01 8:26 ` Jiri Pirko
2017-11-01 13:50 ` John Fastabend [this message]
2017-11-01 13:57 ` Jiri Pirko
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=c76037b1-cc56-5f1f-5893-2b00d4c895f7@gmail.com \
--to=john.fastabend@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=jiri@resnulli.us \
--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