From: Dan Carpenter <dan.carpenter@oracle.com>
To: Hannes Reinecke <hare@suse.de>
Cc: Julia Lawall <julia.lawall@inria.fr>,
Arnd Bergmann <arnd@arndb.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
NeilBrown <neilb@suse.de>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
ksummit@lists.linux.dev
Subject: Re: Potential static analysis ideas
Date: Mon, 26 Jul 2021 12:17:20 +0300 [thread overview]
Message-ID: <20210726091720.GI25548@kadam> (raw)
In-Reply-To: <633614dd-dd88-03f0-c463-d97036c58216@suse.de>
On Mon, Jul 26, 2021 at 11:08:01AM +0200, Hannes Reinecke wrote:
> And that I would consider a coding error.
> If a function is able to return an error pointer it should _always_ return
> an error pointer; here it would be trivial to return -ENXIO instead of NULL
> in the first condition.
>
> Not doing so is just sloppy programming IMO.
>
> Cheers,
But it's not an error. One place where this bit me recently was I was
trying to debug some code and I added:
if (err)
printk("function blah returned err");
But their list iterator returns an error code when it got to the end of
the list so I was flooded with errors. It be nicer "if we can't
allocate enough memory for the next item return an error pointer. If we
come to the end of the loop then return NULL"
regards,
dan carpenter
next prev parent reply other threads:[~2021-07-26 9:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 19:10 Dan Carpenter
2021-07-24 13:33 ` Geert Uytterhoeven
2021-07-24 13:40 ` Julia Lawall
2021-07-24 14:08 ` Arnd Bergmann
2021-07-24 23:18 ` Laurent Pinchart
2021-07-24 23:45 ` NeilBrown
2021-07-26 7:25 ` Arnd Bergmann
2021-07-26 7:53 ` Geert Uytterhoeven
2021-07-26 8:20 ` Arnd Bergmann
2021-07-26 8:39 ` Geert Uytterhoeven
2021-07-26 8:52 ` Arnd Bergmann
2021-07-26 9:11 ` Geert Uytterhoeven
2021-07-26 8:55 ` Julia Lawall
2021-07-26 9:08 ` Hannes Reinecke
2021-07-26 9:16 ` Geert Uytterhoeven
2021-07-26 9:28 ` Julia Lawall
2021-07-26 9:35 ` Hannes Reinecke
2021-07-26 10:03 ` Julia Lawall
2021-07-26 17:54 ` James Bottomley
2021-07-26 18:16 ` Linus Torvalds
2021-07-26 21:53 ` NeilBrown
2021-07-26 18:31 ` Laurent Pinchart
2021-07-26 9:17 ` Dan Carpenter [this message]
2021-07-26 9:13 ` Dan Carpenter
2021-07-26 21:43 ` NeilBrown
2021-07-26 7:05 ` Dan Carpenter
2021-07-26 15:50 ` Paul E. McKenney
2021-07-27 9:38 ` Dan Carpenter
2021-07-27 9:50 ` Geert Uytterhoeven
2021-07-27 16:06 ` Paul E. McKenney
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=20210726091720.GI25548@kadam \
--to=dan.carpenter@oracle.com \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=hare@suse.de \
--cc=julia.lawall@inria.fr \
--cc=ksummit@lists.linux.dev \
--cc=laurent.pinchart@ideasonboard.com \
--cc=neilb@suse.de \
/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