From: David Miller <davem@davemloft.net>
To: dsa@cumulusnetworks.com
Cc: netdev@vger.kernel.org, tgraf@suug.ch
Subject: Re: [PATCH net-next 3/3 v2] net: Allow user to get table id from route lookup
Date: Tue, 15 Sep 2015 12:02:07 -0700 (PDT) [thread overview]
Message-ID: <20150915.120207.715276225859908652.davem@davemloft.net> (raw)
In-Reply-To: <1441227516-39692-3-git-send-email-dsa@cumulusnetworks.com>
From: David Ahern <dsa@cumulusnetworks.com>
Date: Wed, 2 Sep 2015 13:58:36 -0700
> rt_fill_info which is called for 'route get' requests hardcodes the
> table id as RT_TABLE_MAIN which is not correct when multiple tables
> are used. Use the newly added table id in the rtable to send back
> the correct table similar to what is done for IPv6.
>
> To maintain current ABI a new request flag, RTM_F_LOOKUP_TABLE, is
> added to indicate the actual table is wanted versus the hardcoded
> response.
>
> Signed-off-by: David Ahern <dsa@cumulusnetworks.com>
> ---
> v2
> - use a new request flag to indicate the real table id is wanted
> (suggested by Thomas)
Applied.
next prev parent reply other threads:[~2015-09-15 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 20:58 [PATCH net-next 1/3] net: Refactor rtable initialization David Ahern
2015-09-02 20:58 ` [PATCH net-next 2/3] net: Add FIB table id to rtable David Ahern
2015-09-15 19:01 ` David Miller
2015-09-17 6:43 ` Simon Horman
2015-09-02 20:58 ` [PATCH net-next 3/3 v2] net: Allow user to get table id from route lookup David Ahern
2015-09-15 19:02 ` David Miller [this message]
2015-09-15 19:01 ` [PATCH net-next 1/3] net: Refactor rtable initialization David Miller
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=20150915.120207.715276225859908652.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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;
as well as URLs for NNTP newsgroup(s).