From: Claudio Scordino <claudio@evidence.eu.com>
To: "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br>
Cc: linux-mm@kvack.org, philb@gnu.org
Subject: Re: Warning message when compiling ioremap.c
Date: Mon, 08 Sep 2008 15:11:22 +0200 [thread overview]
Message-ID: <48C5247A.1030801@evidence.eu.com> (raw)
In-Reply-To: <20080903140140.333bc137@doriath.conectiva>
[-- Attachment #1: Type: text/plain, Size: 1852 bytes --]
Luiz Fernando N. Capitulino ha scritto:
> Em Tue, 02 Sep 2008 09:37:14 +0200
> Claudio Scordino <claudio@evidence.eu.com> escreveu:
>
> | Hi,
> |
> | I'm not skilled with MM at all, so sorry if I'm saying something
> | stupid.
> |
> | When compiling Linux (latest kernel from Linus' git) on ARM, I noticed
> | the following warning:
> |
> | CC arch/arm/mm/ioremap.o
> | arch/arm/mm/ioremap.c: In function '__arm_ioremap_pfn':
> | arch/arm/mm/ioremap.c:83: warning: control may reach end of non-void
> | function 'remap_area_pte' being inlined
> |
> | According to the message in the printk, we go to "bad" when the page
> | already exists.
>
> You see that right before the return you have added there is a
> BUG() macro? That macro will call panic(), this means that this
> function will never return if it reaches that point.
Well, probably BUG() doesn't call panic() always. For instance, in
arch/arm/include/asm/bug.h in case CONFIG_DEBUG_BUGVERBOSE is defined
(and it might be), BUG just causes an oops (by dereferencing a NULL
pointer). If I'm not wrong this doesn't always mean a panic...
However, in any case, the handler of pagefault eventually calls
do_exit(), so you're right: what follows BUG() won't be executed.
> If all you want is to silent gcc, you should remove the goto and
> move the bad label contents there.
>
> This is minor, but I see no need for the goto.
Yes, it's obviously minor. But I don't like having meaningless
warnings during compilation: they just confuse output, and people may
miss some important warning message...
The need for the goto exists only if BUG() can return, and it doesn't,
so we can safely remove it as you suggested.
Who's in charge of maintaining this piece of code? Should the patch in
attachment be submitted to some specific person?
Many thanks,
Claudio
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Fix-compilation-warning-in-remap_area_pte.patch --]
[-- Type: text/x-diff; name="0001-Fix-compilation-warning-in-remap_area_pte.patch", Size: 0 bytes --]
next prev parent reply other threads:[~2008-09-08 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 7:37 Claudio Scordino
2008-09-03 17:01 ` Luiz Fernando N. Capitulino
2008-09-08 13:11 ` Claudio Scordino [this message]
2008-09-08 13:19 ` Phil Blundell
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=48C5247A.1030801@evidence.eu.com \
--to=claudio@evidence.eu.com \
--cc=lcapitulino@mandriva.com.br \
--cc=linux-mm@kvack.org \
--cc=philb@gnu.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