[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171004150119.GA3840@stefanha-x1.localdomain>
Date: Wed, 4 Oct 2017 11:01:19 -0400
From: Stefan Hajnoczi <stefanha@...hat.com>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: netdev@...r.kernel.org, Jorgen Hansen <jhansen@...are.com>,
Dexuan Cui <decui@...rosoft.com>
Subject: Re: [PATCH iproute2 1/3] ss: allow AF_FAMILY constants >32
On Tue, Oct 03, 2017 at 11:26:53AM -0700, Stephen Hemminger wrote:
> On Tue, 3 Oct 2017 13:57:42 -0400
> Stefan Hajnoczi <stefanha@...hat.com> wrote:
>
> > Linux has more than 32 address families defined in <bits/socket.h>. Use
> > a 64-bit type so all of them can be represented in the filter->families
> > bitmask.
> >
> > It's easy to introduce bugs when using (1 << AF_FAMILY) because the
> > value is 32-bit. This can produce incorrect results from bitmask
> > operations so introduce the FAMILY_MASK() macro to eliminate these bugs.
> >
> > Signed-off-by: Stefan Hajnoczi <stefanha@...hat.com>
> > ---
> > misc/ss.c | 54 ++++++++++++++++++++++++++++--------------------------
> > 1 file changed, 28 insertions(+), 26 deletions(-)
> >
> > diff --git a/misc/ss.c b/misc/ss.c
> > index dd8dfaa4..12a31c90 100644
> > --- a/misc/ss.c
> > +++ b/misc/ss.c
> > @@ -170,55 +170,57 @@ enum {
> > struct filter {
> > int dbs;
> > int states;
> > - int families;
> > + __u64 families;
>
> Since this isn't a value that is coming from kernel. It should be uint64_t
> rather than __u64.
Okay, will fix in v2.
Powered by blists - more mailing lists