netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cong Wang <xiyou.wangcong@gmail.com>
To: Vlad Buslov <vladbu@mellanox.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
	Jiri Pirko <jiri@resnulli.us>,
	Jamal Hadi Salim <jhs@mojatatu.com>
Subject: Re: [Patch net-next] net_sched: fix an extack message in tcf_block_find()
Date: Fri, 28 Sep 2018 10:03:08 -0700	[thread overview]
Message-ID: <CAM_iQpVB8_H7-DX=GY1wCNEf0PCm53Zx7mOZ7AkmnGGOpO+WTw@mail.gmail.com> (raw)
In-Reply-To: <vbf1s9dyhub.fsf@reg-r-vrt-018-180.mtr.labs.mlnx>

On Fri, Sep 28, 2018 at 4:36 AM Vlad Buslov <vladbu@mellanox.com> wrote:
>
> On Thu 27 Sep 2018 at 20:42, Cong Wang <xiyou.wangcong@gmail.com> wrote:
> > It is clearly a copy-n-paste.
> >
> > Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com>
> > ---
> >  net/sched/cls_api.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/net/sched/cls_api.c b/net/sched/cls_api.c
> > index 3de47e99b788..8dd7f8af6d54 100644
> > --- a/net/sched/cls_api.c
> > +++ b/net/sched/cls_api.c
> > @@ -655,7 +655,7 @@ static struct tcf_block *tcf_block_find(struct net *net, struct Qdisc **q,
> >
> >               *q = qdisc_refcount_inc_nz(*q);
> >               if (!*q) {
> > -                     NL_SET_ERR_MSG(extack, "Parent Qdisc doesn't exists");
> > +                     NL_SET_ERR_MSG(extack, "Can't increase Qdisc refcount");
> >                       err = -EINVAL;
> >                       goto errout_rcu;
> >               }
>
> Is there a benefit in exposing this info to user?

Depends on what user you mean here. For kernel developers, yes,
this is useful. For others, no.


> For all intents and purposes Qdisc is gone at that point.

I don't want to be a language lawyer, but there is a difference between
"it doesn't exist" and "it exists but being removed". The errno EINVAL
betrays what you said too, it must be ENOENT to mach "Qdisc is gone".

I don't want to waste my time on this any more. Let's just drop it.

I really don't care, do you?

  reply	other threads:[~2018-09-28 23:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-27 20:42 [Patch net-next] net_sched: fix an extack message in tcf_block_find() Cong Wang
2018-09-27 20:42 ` [Patch net-next] net_sched: fix a crash in tc_new_tfilter() Cong Wang
2018-09-27 21:16 ` [Patch net-next] net_sched: fix an extack message in tcf_block_find() Eric Dumazet
2018-09-27 21:36   ` Cong Wang
2018-09-27 22:18     ` Eric Dumazet
2018-09-28 17:19       ` rcu_read_lock() " Cong Wang
2018-09-28  1:51     ` [Patch net-next] net_sched: fix an extack message " David Ahern
2018-09-28 11:36 ` Vlad Buslov
2018-09-28 17:03   ` Cong Wang [this message]
2018-09-30 14:12     ` Vlad Buslov
2018-09-28 17:04 ` Cong Wang

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='CAM_iQpVB8_H7-DX=GY1wCNEf0PCm53Zx7mOZ7AkmnGGOpO+WTw@mail.gmail.com' \
    --to=xiyou.wangcong@gmail.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=vladbu@mellanox.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;
as well as URLs for NNTP newsgroup(s).