From: David Miller <davem@davemloft.net>
To: lorenzo@google.com
Cc: john.stultz@linaro.org, dsa@cumulusnetworks.com,
mateusz.bajorski@nokia.com, linux-kernel@vger.kernel.org,
guodong.xu@linaro.org, dimitrysh@google.com, chh@google.com,
ejcaruso@google.com, romlem@google.com
Subject: Re: [Regression?] fib_rules: Added NLM_F_EXCL support to fib_nl_newrule breaks Android userspace
Date: Tue, 02 Aug 2016 18:04:31 -0700 (PDT) [thread overview]
Message-ID: <20160802.180431.1364387950717991600.davem@davemloft.net> (raw)
In-Reply-To: <CAKD1Yr3krJ3efY1WKNTxWxrRXh9hmXRjeVVK7KZyEWHW8JENVA@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 3 Aug 2016 09:58:09 +0900
> The problem is that the UID routing patches were never accepted
> upstream, and because FRA_xxx and RTA_xxx are enums, there's no safe
> way to add a new value out of tree like there would be with other
> identifiers such as setsockopt values.
>
> I'm going to make another attempt to upstream the UID routing code
> soon. If that doesn't make it, then we could attempt to reserve a
> couple RTA_xxx and FRA_xxx values for local use.
If upstream rejects the feature, it's because you'll be given a
suggested alternative implementation in order to achieve your
goals.
In that respect, it is inappropriate to expect that we will "reserve"
netlink ID space for such a feature that is rejected in that manner
upstream.
prev parent reply other threads:[~2016-08-03 1:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 4:18 John Stultz
2016-07-29 4:20 ` David Miller
2016-07-29 14:12 ` David Ahern
2016-07-29 16:57 ` John Stultz
2016-07-29 19:10 ` David Ahern
2016-08-01 1:42 ` Lorenzo Colitti
2016-08-02 16:37 ` John Stultz
2016-08-02 17:03 ` John Stultz
2016-08-02 17:09 ` David Ahern
2016-08-02 17:51 ` John Stultz
2016-08-02 18:00 ` David Miller
2016-08-02 18:22 ` John Stultz
2016-08-02 18:28 ` David Miller
2016-08-03 0:58 ` Lorenzo Colitti
2016-08-03 1:04 ` 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=20160802.180431.1364387950717991600.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=chh@google.com \
--cc=dimitrysh@google.com \
--cc=dsa@cumulusnetworks.com \
--cc=ejcaruso@google.com \
--cc=guodong.xu@linaro.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@google.com \
--cc=mateusz.bajorski@nokia.com \
--cc=romlem@google.com \
/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
all inboxes | Powered by JetHome®