From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: IS_ERR_VALUE()
Date: Tue, 12 Mar 2013 20:56:59 +0100 [thread overview]
Message-ID: <20130312195659.GR15375@pengutronix.de> (raw)
In-Reply-To: <20130312141604.GV4977@n2100.arm.linux.org.uk>
Hello,
On Tue, Mar 12, 2013 at 02:16:04PM +0000, Russell King - ARM Linux wrote:
> I am removing almost all references to the above macro from arch/arm.
> Many of them are wrong. Some of them are buggy.
>
> For instance:
>
> int gpmc_cs_set_timings(int cs, const struct gpmc_timings *t)
> {
> int div;
> div = gpmc_calc_divider(t->sync_clk);
> if (div < 0)
> return div;
> static int gpmc_set_async_mode(int cs, struct gpmc_timings *t)
> {
> ...
> return gpmc_cs_set_timings(cs, t);
>
> .....
> ret = gpmc_set_async_mode(gpmc_onenand_data->cs, &t);
> if (IS_ERR_VALUE(ret))
> return ret;
Well, gpmc_calc_divider returns -1 on failure, so I agree that it's
wrong to use IS_ERR_VALUE on it.
> So, gpmc_cs_set_timings() thinks any negative return value is an error,
> but where we check that in higher levels, only a limited range are
> errors... seriously? Come on guys, get with the program. Get your
> error checking in order.
Still I don't get what is really wrong in your examples (but I didn't
check all). If a function returning an int is supposed to return 0 on
success and -ESOMEERROR on failure it doesn't matter much if I do (ret <
0) or IS_ERR_VALUE(ret). (Even if ret is signed, the check (x) >=
(unsigned long)-MAX_ERRNO in IS_ERR_VALUE does the right thing.)
There is only a semantical difference between the two checks for
(unsigned)ret being between MAX_INT+1 and (unsigned)-MAX_ERRNO. But a
value in this range isn't allowed for such a function. So you could also
just check using "if (ret)". All but the previous sentence also apply to
functions returning an int >=0 on success and -ESOMEERROR on failure.
So unless I missed something---and if I do, please tell me---your patch
is not about correctness, but "only" about style and consistency?!
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2013-03-12 19:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 14:16 IS_ERR_VALUE() Russell King - ARM Linux
2013-03-12 16:34 ` IS_ERR_VALUE() Tony Lindgren
2013-03-12 19:56 ` Uwe Kleine-König [this message]
2013-03-12 20:22 ` IS_ERR_VALUE() Russell King - ARM Linux
2013-03-12 21:18 ` IS_ERR_VALUE() Uwe Kleine-König
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=20130312195659.GR15375@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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).