From: <Daniel.Machon@microchip.com>
To: <petrm@nvidia.com>
Cc: <netdev@vger.kernel.org>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<joe@perches.com>, <vladimir.oltean@nxp.com>,
<linux-kernel@vger.kernel.org>, <UNGLinuxDriver@microchip.com>,
<lkp@intel.com>
Subject: Re: [PATCH net-next] net: dcb: move getapptrust to separate function
Date: Fri, 11 Nov 2022 06:45:18 +0000 [thread overview]
Message-ID: <Y23x/PSlybLqaQIS@DEN-LT-70577> (raw)
In-Reply-To: <87eduaoj8g.fsf@nvidia.com>
Den Thu, Nov 10, 2022 at 05:30:43PM +0100 skrev Petr Machata:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Daniel Machon <daniel.machon@microchip.com> writes:
>
> > diff --git a/net/dcb/dcbnl.c b/net/dcb/dcbnl.c
> > index cec0632f96db..3f4d88c1ec78 100644
> > --- a/net/dcb/dcbnl.c
> > +++ b/net/dcb/dcbnl.c
> > @@ -1060,11 +1060,52 @@ static int dcbnl_build_peer_app(struct net_device *netdev, struct sk_buff* skb,
> > return err;
> > }
> >
> > +static int dcbnl_getapptrust(struct net_device *netdev, struct sk_buff *skb)
> > +{
> > + const struct dcbnl_rtnl_ops *ops = netdev->dcbnl_ops;
> > + int nselectors, err;
> > + u8 *selectors;
> > +
> > + selectors = kzalloc(IEEE_8021QAZ_APP_SEL_MAX + 1, GFP_KERNEL);
> > + if (!selectors)
> > + return -ENOMEM;
> > +
> > + err = ops->dcbnl_getapptrust(netdev, selectors, &nselectors);
> > +
> > + if (!err) {
> > + struct nlattr *apptrust;
> > + int i;
>
> (Maybe consider moving these up to the function scope. This scope
> business made sense in the generic function, IMHO is not as useful with
> a focused function like this one.)
I dont mind doing that, however, this 'scope business' is just staying true
to the rest of the dcbnl code :-) - that said, I think I agree with your
point.
>
> > +
> > + err = -EMSGSIZE;
> > +
> > + apptrust = nla_nest_start(skb, DCB_ATTR_DCB_APP_TRUST_TABLE);
> > + if (!apptrust)
> > + goto nla_put_failure;
> > +
> > + for (i = 0; i < nselectors; i++) {
> > + enum ieee_attrs_app type =
> > + dcbnl_app_attr_type_get(selectors[i]);
>
> Doesn't checkpatch warn about this? There should be a blank line after
> the variable declaration block. (Even if there wasn't one there in the
> original code either.)
Nope, no warning. And I think it has something to do with the way the line
is split.
>
> > + err = nla_put_u8(skb, type, selectors[i]);
> > + if (err) {
> > + nla_nest_cancel(skb, apptrust);
> > + goto nla_put_failure;
> > + }
> > + }
> > + nla_nest_end(skb, apptrust);
> > + }
> > +
> > + err = 0;
> > +
> > +nla_put_failure:
> > + kfree(selectors);
> > + return err;
> > +}
> > +
next prev parent reply other threads:[~2022-11-11 6:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 9:46 [PATCH net-next] net: dcb: move getapptrust to separate function Daniel Machon
2022-11-10 16:30 ` Petr Machata
2022-11-11 6:45 ` Daniel.Machon [this message]
2022-11-11 11:24 ` Petr Machata
2022-11-11 12:47 ` Joe Perches
2022-11-14 8:45 ` Daniel.Machon
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=Y23x/PSlybLqaQIS@DEN-LT-70577 \
--to=daniel.machon@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=joe@perches.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=vladimir.oltean@nxp.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).