[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190702151422.6b2685f4@hermes.lan>
Date: Tue, 2 Jul 2019 15:14:22 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: David Miller <davem@...emloft.net>
Cc: kuznet@....inr.ac.ru, yoshfuji@...ux-ipv6.org,
netdev@...r.kernel.org
Subject: Re: [PATCH net] net: don't warn in inet diag when IPV6 is disabled
On Tue, 02 Jul 2019 14:23:47 -0700 (PDT)
David Miller <davem@...emloft.net> wrote:
> From: Stephen Hemminger <stephen@...workplumber.org>
> Date: Mon, 1 Jul 2019 08:23:03 -0700
>
> > @@ -19,9 +19,11 @@ raw_get_hashinfo(const struct inet_diag_req_v2 *r)
> > {
> > if (r->sdiag_family == AF_INET) {
> > return &raw_v4_hashinfo;
> > -#if IS_ENABLED(CONFIG_IPV6)
> > } else if (r->sdiag_family == AF_INET6) {
> > +#if IS_ENABLED(CONFIG_IPV6)
> > return &raw_v6_hashinfo;
> > +#else
> > + return ERR_PTR(-EOPNOTSUPP);
> > #endif
> > } else {
> > pr_warn_once("Unexpected inet family %d\n",
>
> Let's make some consistency in this area please.
>
> The inet_diag code returns -EINVAL, and that's been that way forever.
> It also doesn't print a weird warning for unexpected sdiag_family
> values outside of AF_INET and AF_INET6.
>
> That's been that way for so long that's probably the behavior to
> revolve everything around.
>
> Therefore, please just get rid of the warning message instead of
> all of these other changes.
>
> Thank you.
Sure, that makes sense.
Powered by blists - more mailing lists