From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-s390@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Claudio Imbrenda <imbrenda@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org,
Gerald Schaefer <gerald.schaefer@de.ibm.com>,
Souptick Joarder <jrdr.linux@gmail.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Philipp Rudo <prudo@linux.ibm.com>
Subject: Re: [PATCH] s390: add unreachable() to dump_fault_info() to fix -Wmaybe-uninitialized
Date: Fri, 17 May 2019 09:06:26 +0200 [thread overview]
Message-ID: <20190517090626.3c707d77@mschwideX1> (raw)
In-Reply-To: <20190517064922.22743-1-yamada.masahiro@socionext.com>
On Fri, 17 May 2019 15:49:22 +0900
Masahiro Yamada <yamada.masahiro@socionext.com> wrote:
> When CONFIG_OPTIMIZE_INLINING is enabled for s390, I see this warning:
>
> arch/s390/mm/fault.c:127:15: warning: 'asce' may be used uninitialized in this function [-Wmaybe-uninitialized]
> switch (asce & _ASCE_TYPE_MASK) {
> arch/s390/mm/fault.c:177:16: note: 'asce' was declared here
> unsigned long asce;
> ^~~~
>
> If get_fault_type() is not inlined, the compiler cannot deduce that
> all the possible paths in the 'switch' statement are covered.
>
> Of course, we could mark get_fault_type() as __always_inline to get
> back the original behavior, but I do not think it sensible to force
> inlining just for the purpose of suppressing the warning. Since this
> is just a matter of warning, I want to keep as much room for compiler
> optimization as possible.
>
> I added unreachable() to teach the compiler that the 'default' label
> is unreachable.
>
> I got rid of the 'inline' marker. Even without the 'inline' hint,
> the compiler inlines functions based on its inlining heuristic.
>
> Fixes: 9012d011660e ("compiler: allow all arches to enable CONFIG_OPTIMIZE_INLINING")
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Added to our internal tree and I will add it to s390/linux soon. Thanks.
> ---
>
> arch/s390/mm/fault.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/arch/s390/mm/fault.c b/arch/s390/mm/fault.c
> index c220399ae196..91ce03fd0c84 100644
> --- a/arch/s390/mm/fault.c
> +++ b/arch/s390/mm/fault.c
> @@ -85,7 +85,7 @@ static inline int notify_page_fault(struct pt_regs *regs)
> * Find out which address space caused the exception.
> * Access register mode is impossible, ignore space == 3.
> */
> -static inline enum fault_type get_fault_type(struct pt_regs *regs)
> +static enum fault_type get_fault_type(struct pt_regs *regs)
> {
> unsigned long trans_exc_code;
>
> @@ -211,6 +211,8 @@ static void dump_fault_info(struct pt_regs *regs)
> asce = S390_lowcore.kernel_asce;
> pr_cont("kernel ");
> break;
> + default:
> + unreachable();
> }
> pr_cont("ASCE.\n");
> dump_pagetable(asce, regs->int_parm_long & __FAIL_ADDR_MASK);
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
prev parent reply other threads:[~2019-05-17 7:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 6:49 [PATCH] s390: add unreachable() to dump_fault_info() to fix -Wmaybe-uninitialized Masahiro Yamada
2019-05-17 6:59 ` Sergey Senozhatsky
2019-05-17 7:06 ` Martin Schwidefsky [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=20190517090626.3c707d77@mschwideX1 \
--to=schwidefsky@de.ibm.com \
--cc=arnd@arndb.de \
--cc=gerald.schaefer@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=imbrenda@linux.vnet.ibm.com \
--cc=jrdr.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=prudo@linux.ibm.com \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=yamada.masahiro@socionext.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox