[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM0EoMkYCZovRqu4KRvgoO0YfEf0UXm0tU_uTmfJ5Ln2kbD1mQ@mail.gmail.com>
Date: Sat, 15 Apr 2023 10:06:36 -0400
From: Jamal Hadi Salim <jhs@...atatu.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Pedro Tammela <pctammela@...atatu.com>, netdev@...r.kernel.org,
xiyou.wangcong@...il.com, jiri@...nulli.us, davem@...emloft.net,
edumazet@...gle.com, pabeni@...hat.com
Subject: Re: [PATCH net-next 1/2] net/sched: sch_htb: use extack on errors messages
On Fri, Apr 14, 2023 at 9:13 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Fri, 14 Apr 2023 15:53:09 -0300 Pedro Tammela wrote:
> > @@ -1917,8 +1917,9 @@ static int htb_change_class(struct Qdisc *sch, u32 classid,
> > };
> > err = htb_offload(dev, &offload_opt);
> > if (err) {
> > - pr_err("htb: TC_HTB_LEAF_ALLOC_QUEUE failed with err = %d\n",
> > - err);
> > + NL_SET_ERR_MSG_FMT_MOD(extack,
>
> What's the ruling on using _MOD() in qdiscs ?
> There are some extacks already in this file without _MOD().
There is no "rule" other than the LinuxWay(tm) i.e. people cutnpaste.
It's not just on qdiscs that this inconsistency exists but also on
filters and actions.
Do we need a rule to prefer one over the other? _MOD() seems to
provide more information - which is always useful.
cheers,
jamal
Powered by blists - more mailing lists