mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: will@kernel.org, catalin.marinas@arm.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
	Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH 1/3] arm64: perf: Mark expected switch fall-through
Date: Fri, 26 Jul 2019 13:10:57 +0100	[thread overview]
Message-ID: <20190726121056.GA26088@lakrids.cambridge.arm.com> (raw)
In-Reply-To: <20190726112716.19104-1-anders.roxell@linaro.org>

On Fri, Jul 26, 2019 at 01:27:16PM +0200, Anders Roxell wrote:
> When fall-through warnings was enabled by default, commit d93512ef0f0e
> ("Makefile: Globally enable fall-through warning"), the following
> warnings was starting to show up:
> 
> ../arch/arm64/kernel/hw_breakpoint.c: In function ‘hw_breakpoint_arch_parse’:
> ../arch/arm64/kernel/hw_breakpoint.c:540:7: warning: this statement may fall
>  through [-Wimplicit-fallthrough=]
>     if (hw->ctrl.len == ARM_BREAKPOINT_LEN_1)
>        ^
> ../arch/arm64/kernel/hw_breakpoint.c:542:3: note: here
>    case 2:
>    ^~~~
> ../arch/arm64/kernel/hw_breakpoint.c:544:7: warning: this statement may fall
>  through [-Wimplicit-fallthrough=]
>     if (hw->ctrl.len == ARM_BREAKPOINT_LEN_2)
>        ^
> ../arch/arm64/kernel/hw_breakpoint.c:546:3: note: here
>    default:
>    ^~~~~~~
> 
> Rework so that the compiler doesn't warn about fall-through. Rework so
> the code looks like the arm code. Since the comment in the function
> indicates taht this is supposed to behave the same way as arm32 because

Typo: s/taht/that/

> it handles 32-bit tasks also.
> 
> Cc: stable@vger.kernel.org # v3.16+
> Fixes: 6ee33c2712fc ("ARM: hw_breakpoint: correct and simplify alignment fixup code")
> Signed-off-by: Anders Roxell <anders.roxell@linaro.org>

The patch itself looks fine, but I don't think this needs a CC to
stable, nor does it require that fixes tag, as there's no functional
problem.

If anything, it fixes:

  d93512ef0f0e (" Makefile: Globally enable fall-through warning")

... given the commit message for that patch states:

  Now that all the fall-through warnings have been addressed in the
  kernel, enable the fall-through warning globally.

... and the existence of this patch implies otherwise.

IIUC that patch isn't even in mainline yet, but given this is simple I
imagine that Will and Catalin might be happy to pick this up for the
next rc.

Thanks,
Mark.

> ---
>  arch/arm64/kernel/hw_breakpoint.c | 11 +++++++----
>  1 file changed, 7 insertions(+), 4 deletions(-)
> 
> diff --git a/arch/arm64/kernel/hw_breakpoint.c b/arch/arm64/kernel/hw_breakpoint.c
> index dceb84520948..ea616adf1cf1 100644
> --- a/arch/arm64/kernel/hw_breakpoint.c
> +++ b/arch/arm64/kernel/hw_breakpoint.c
> @@ -535,14 +535,17 @@ int hw_breakpoint_arch_parse(struct perf_event *bp,
>  		case 0:
>  			/* Aligned */
>  			break;
> -		case 1:
> -			/* Allow single byte watchpoint. */
> -			if (hw->ctrl.len == ARM_BREAKPOINT_LEN_1)
> -				break;
>  		case 2:
>  			/* Allow halfword watchpoints and breakpoints. */
>  			if (hw->ctrl.len == ARM_BREAKPOINT_LEN_2)
>  				break;
> +			/* Fall through */
> +		case 1:
> +		case 3:
> +			/* Allow single byte watchpoint. */
> +			if (hw->ctrl.len == ARM_BREAKPOINT_LEN_1)
> +				break;
> +			/* Fall through */
>  		default:
>  			return -EINVAL;
>  		}
> -- 
> 2.20.1
> 

  reply	other threads:[~2019-07-26 12:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-26 11:27 Anders Roxell
2019-07-26 12:10 ` Mark Rutland [this message]
2019-07-26 12:13   ` Mark Rutland
2019-07-26 12:27     ` Will Deacon
2019-07-26 12:38       ` Robin Murphy
2019-07-26 13:05         ` Will Deacon
2019-07-26 13:28           ` Robin Murphy

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=20190726121056.GA26088@lakrids.cambridge.arm.com \
    --to=mark.rutland@arm.com \
    --cc=anders.roxell@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=gustavo@embeddedor.com \
    --cc=keescook@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=will@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®