From: Jason Wessel <jason.wessel@windriver.com>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Daniel Thompson <daniel.thompson@linaro.org>
Cc: <kgdb-bugreport@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>, Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH] gdbstub: mark expected switch fall-throughs
Date: Tue, 26 Feb 2019 14:47:28 -0600 [thread overview]
Message-ID: <d0ae1626-1a41-55c5-cfe9-0dea3edc98f9@windriver.com> (raw)
In-Reply-To: <20190226191614.GA21908@embeddedor>
We'll have to fix them at some point.
Acked-by: Jason Wessel <jason.wessel@windriver.com>
Cheers,
Jason.
On 2/26/19 1:16 PM, Gustavo A. R. Silva wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> This patch fixes the following warnings:
>
> kernel/debug/gdbstub.c: In function ‘gdb_serial_stub’:
> kernel/debug/gdbstub.c:1031:7: warning: this statement may fall through [-Wimplicit-fallthrough=]
> if (remcom_in_buffer[1] == '\0') {
> ^
> kernel/debug/gdbstub.c:1036:3: note: here
> case 'C': /* Exception passing */
> ^~~~
> kernel/debug/gdbstub.c:1040:7: warning: this statement may fall through [-Wimplicit-fallthrough=]
> if (tmp == 0)
> ^
> kernel/debug/gdbstub.c:1043:3: note: here
> case 'c': /* Continue packet */
> ^~~~
> kernel/debug/gdbstub.c:1050:4: warning: this statement may fall through [-Wimplicit-fallthrough=]
> dbg_activate_sw_breakpoints();
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> kernel/debug/gdbstub.c:1052:3: note: here
> default:
> ^~~~~~~
>
> Warning level 3 was used: -Wimplicit-fallthrough=3
>
> Notice that, in this particular case, the code comment is modified
> in accordance with what GCC is expecting to find.
>
> This patch is part of the ongoing efforts to enable
> -Wimplicit-fallthrough.
>
> Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
> ---
> kernel/debug/gdbstub.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/debug/gdbstub.c b/kernel/debug/gdbstub.c
> index 7510dc687c0d..9f267b8905b4 100644
> --- a/kernel/debug/gdbstub.c
> +++ b/kernel/debug/gdbstub.c
> @@ -1033,13 +1033,14 @@ int gdb_serial_stub(struct kgdb_state *ks)
> return DBG_PASS_EVENT;
> }
> #endif
> + /* Fall through */
> case 'C': /* Exception passing */
> tmp = gdb_cmd_exception_pass(ks);
> if (tmp > 0)
> goto default_handle;
> if (tmp == 0)
> break;
> - /* Fall through on tmp < 0 */
> + /* Fall through - on tmp < 0 */
> case 'c': /* Continue packet */
> case 's': /* Single step packet */
> if (kgdb_contthread && kgdb_contthread != current) {
> @@ -1048,7 +1049,7 @@ int gdb_serial_stub(struct kgdb_state *ks)
> break;
> }
> dbg_activate_sw_breakpoints();
> - /* Fall through to default processing */
> + /* Fall through - to default processing */
> default:
> default_handle:
> error = kgdb_arch_handle_exception(ks->ex_vector,
>
next prev parent reply other threads:[~2019-02-26 20:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 19:16 Gustavo A. R. Silva
2019-02-26 20:47 ` Jason Wessel [this message]
2019-02-26 20:59 ` Gustavo A. R. Silva
2019-04-01 19:57 ` Gustavo A. R. Silva
2019-04-04 10:12 ` Daniel Thompson
2019-04-04 16:02 ` Gustavo A. R. Silva
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=d0ae1626-1a41-55c5-cfe9-0dea3edc98f9@windriver.com \
--to=jason.wessel@windriver.com \
--cc=daniel.thompson@linaro.org \
--cc=gustavo@embeddedor.com \
--cc=keescook@chromium.org \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®