netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivan Vecera <ivecera@redhat.com>
To: Michal Kubecek <mkubecek@suse.cz>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH ethtool 1/2] netlink: return -ENOMEM when calloc fails
Date: Mon, 28 Sep 2020 21:21:42 +0200	[thread overview]
Message-ID: <20200928212142.03afa116@ceranb> (raw)
In-Reply-To: <20200928154455.hi6767brao7p4ac5@lion.mk-sys.cz>

On Mon, 28 Sep 2020 17:44:55 +0200
Michal Kubecek <mkubecek@suse.cz> wrote:

> On Thu, Sep 24, 2020 at 09:27:57PM +0200, Ivan Vecera wrote:
> > Fixes: f2c17e107900 ("netlink: add netlink handler for gfeatures (-k)")
> > 
> > Cc: Michal Kubecek <mkubecek@suse.cz>
> > Signed-off-by: Ivan Vecera <ivecera@redhat.com>
> > ---
> >  netlink/features.c | 9 +++++----
> >  1 file changed, 5 insertions(+), 4 deletions(-)
> > 
> > diff --git a/netlink/features.c b/netlink/features.c
> > index 3f1240437350..b2cf57eea660 100644
> > --- a/netlink/features.c
> > +++ b/netlink/features.c
> > @@ -112,16 +112,17 @@ int dump_features(const struct nlattr *const *tb,
> >  	unsigned int *feature_flags = NULL;
> >  	struct feature_results results;
> >  	unsigned int i, j;
> > -	int ret;
> > +	int ret = 0;
> >  
> >  	ret = prepare_feature_results(tb, &results);
> >  	if (ret < 0)
> >  		return -EFAULT;
> >  
> > -	ret = -ENOMEM;
> >  	feature_flags = calloc(results.count, sizeof(feature_flags[0]));
> > -	if (!feature_flags)
> > +	if (!feature_flags) {
> > +		ret = -ENOMEM;
> >  		goto out_free;
> > +	}
> >  
> >  	/* map netdev features to legacy flags */
> >  	for (i = 0; i < results.count; i++) {
> > @@ -184,7 +185,7 @@ int dump_features(const struct nlattr *const *tb,
> >  
> >  out_free:
> >  	free(feature_flags);
> > -	return 0;
> > +	return ret;
> >  }
> >  
> >  int features_reply_cb(const struct nlmsghdr *nlhdr, void *data)
> > -- 
> > 2.26.2  
> 
> The patch is correct but relying on ret staying zero through the whole
> function is rather fragile (it could break when adding more checks in
> the future) and it also isn't consistent with the way this is done in
> other functions.
> 
> AFAICS you could omit the first hunk and just add "ret = 0" above the
> out_free label.
> 
> Michal

OK, will do.

Ivan


      reply	other threads:[~2020-09-28 19:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-24 19:27 [PATCH ethtool 1/2] netlink: return -ENOMEM when calloc fails Ivan Vecera
2020-09-24 19:27 ` [PATCH ethtool 2/2] netlink: fix memory leak Ivan Vecera
2020-09-28 15:37   ` Michal Kubecek
2020-09-28 15:44 ` [PATCH ethtool 1/2] netlink: return -ENOMEM when calloc fails Michal Kubecek
2020-09-28 19:21   ` Ivan Vecera [this message]

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=20200928212142.03afa116@ceranb \
    --to=ivecera@redhat.com \
    --cc=mkubecek@suse.cz \
    --cc=netdev@vger.kernel.org \
    /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).