All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsa@cumulusnetworks.com>
To: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: Make table id type u32
Date: Tue, 1 Sep 2015 12:39:54 -0600	[thread overview]
Message-ID: <55E5F0FA.4080909@cumulusnetworks.com> (raw)
In-Reply-To: <E82296F9-9C96-4589-B85B-0D12FB7BAAF4@cumulusnetworks.com>

On 9/1/15 12:39 PM, Nikolay Aleksandrov wrote:
>
>> On Sep 1, 2015, at 11:25 AM, David Ahern <dsa@cumulusnetworks.com> wrote:
>>
>> for net-next. Forgot to add to subject line. (Thanks, Roopa, for the reminder.)
>>
>> On 9/1/15 12:18 PM, David Ahern wrote:
>>> A number of VRF patches used 'int' for table id. It should be u32 to be
>>> consistent with the rest of the stack.
>>>
>>> Fixes:
>>> 4e3c89920cd3a ("net: Introduce VRF related flags and helpers")
>>> 15be405eb2ea9 ("net: Add inet_addr lookup by table")
>>> 30bbaa1950055 ("net: Fix up inet_addr_type checks")
>>> 021dd3b8a142d ("net: Add routes to the table associated with the device")
>>> dc028da54ed35 ("inet: Move VRF table lookup to inlined function")
>>>
>>> Signed-off-by: David Ahern <dsa@cumulusnetworks.com>
>>> ---
>>>   include/net/route.h      |  2 +-
>>>   include/net/vrf.h        | 24 ++++++++++++------------
>>>   net/ipv4/af_inet.c       |  2 +-
>>>   net/ipv4/fib_frontend.c  | 10 +++++-----
>>>   net/ipv4/fib_semantics.c |  2 +-
>>>   5 files changed, 20 insertions(+), 20 deletions(-)
> <<snip>>
>
> Should the fib_table_lookup tracepoint be updated as well ? It seems to be using
> int for tb_id even though it’s a u32 in struct fib_table.
>

yes. good catch.

      reply	other threads:[~2015-09-01 18:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01 18:18 [PATCH] net: Make table id type u32 David Ahern
2015-09-01 18:25 ` [PATCH net-next] " David Ahern
2015-09-01 18:39   ` Nikolay Aleksandrov
2015-09-01 18:39     ` David Ahern [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=55E5F0FA.4080909@cumulusnetworks.com \
    --to=dsa@cumulusnetworks.com \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@cumulusnetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.