From: Arnd Bergmann <arnd@arndb.de>
To: Andrzej Hajda <a.hajda@samsung.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
open list <linux-kernel@vger.kernel.org>,
Bob Peterson <rpeterso@redhat.com>
Subject: Re: [PATCH v3] err.h: allow IS_ERR_VALUE to handle properly more types
Date: Thu, 04 Feb 2016 16:00:09 +0100 [thread overview]
Message-ID: <2230609.SaGfiizDHl@wuerfel> (raw)
In-Reply-To: <56B363E3.9050007@samsung.com>
On Thursday 04 February 2016 15:44:51 Andrzej Hajda wrote:
> On 02/04/2016 01:40 PM, Arnd Bergmann wrote:
> > On Wednesday 03 February 2016 14:15:28 Andrzej Hajda wrote:
> >> diff --git a/include/linux/err.h b/include/linux/err.h
> >> index 56762ab..b7d4a9f 100644
> >> --- a/include/linux/err.h
> >> +++ b/include/linux/err.h
> >> @@ -18,7 +18,9 @@
> >>
> >> #ifndef __ASSEMBLY__
> >>
> >> -#define IS_ERR_VALUE(x) unlikely((x) >= (unsigned long)-MAX_ERRNO)
> >> +#define IS_ERR_VALUE(x) ((typeof(x))(-1) <= 0 \
> >> + ? unlikely((x) <= -1) \
> >> + : unlikely((x) >= (typeof(x))-MAX_ERRNO))
> >>
> >> static inline void * __must_check ERR_PTR(long error)
> >> {
> >>
> > This has caused a warning to reappear that I had fixed before:
> >
> > fs/gfs2/dir.c: In function 'get_first_leaf':
> > fs/gfs2/dir.c:802:9: warning: 'leaf_no' may be used uninitialized in this function [-Wmaybe-uninitialized]
> > error = get_leaf(dip, leaf_no, bh_out);
> > ^
> > fs/gfs2/dir.c: In function 'dir_split_leaf':
> > fs/gfs2/dir.c:1021:8: warning: 'leaf_no' may be used uninitialized in this function [-Wmaybe-uninitialized]
> > error = get_leaf(dip, leaf_no, &obh);
>
> What gcc/arch/build options do you use? I cannot reproduce it in my
> environment.
>
I use an ARM gcc-5.3 with an allmodconfig kernel and CONFIG_CC_OPTIMIZE_FOR_SIZE
disabled. I see the same warning with any gcc version since 4.9, but not earlier.
With the IS_ERR_VALUE() macro I sent, I don't see the warning on any gcc
version. I have now also checked that the behavior on x86 gcc-.4.9 is the
same that I see on ARM (I don't have a large collection of x86 gcc versions
though): same warning with linux-next, no warning with my version or after
reverting your patch.
Arnd
next prev parent reply other threads:[~2016-02-04 15:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 14:58 [PATCH] err.h: allow IS_ERR_VALUE to handle properly more types Andrzej Hajda
2016-01-07 15:48 ` kbuild test robot
2016-01-28 8:27 ` [PATCH v2] " Andrzej Hajda
2016-02-02 6:23 ` Andrew Morton
2016-02-02 8:22 ` Andrzej Hajda
2016-02-03 0:33 ` Andrew Morton
2016-02-03 10:53 ` Andrzej Hajda
2016-02-03 13:15 ` [PATCH v3] " Andrzej Hajda
2016-02-04 12:40 ` Arnd Bergmann
2016-02-04 14:44 ` Andrzej Hajda
2016-02-04 15:00 ` Arnd Bergmann [this message]
2016-02-04 15:10 ` Arnd Bergmann
2016-02-04 18:59 ` Andrew Morton
2016-02-05 10:52 ` Arnd Bergmann
2016-02-08 8:45 ` Andrzej Hajda
2016-02-08 12:01 ` Arnd Bergmann
2016-02-09 1:44 ` Al Viro
2016-02-09 8:42 ` Andrzej Hajda
2016-02-10 21:01 ` Arnd Bergmann
2016-02-11 7:00 ` Andrzej Hajda
2016-02-11 16:39 ` Arnd Bergmann
2016-02-12 14:45 ` Andrzej Hajda
2016-02-11 21:14 ` Al Viro
2016-02-04 23:37 ` Rasmus Villemoes
2016-02-10 15:16 ` Guenter Roeck
2016-01-15 13:45 ` [PATCH] " Andrzej Hajda
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=2230609.SaGfiizDHl@wuerfel \
--to=arnd@arndb.de \
--cc=a.hajda@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=b.zolnierkie@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=rpeterso@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.