public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Osama Abdelkader <osama.abdelkader@gmail.com>
Cc: smostafa@google.com, catalin.marinas@arm.com,
	linux-kernel@vger.kernel.org, will@kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: Remove unreachable break after die
Date: Thu, 27 Nov 2025 09:20:57 +0000	[thread overview]
Message-ID: <aSgX-br67x5Y-kBZ@J2N7QTR9R3> (raw)
In-Reply-To: <20251126222620.215245-1-osama.abdelkader@gmail.com>

On Thu, Nov 27, 2025 at 12:26:20AM +0200, Osama Abdelkader wrote:
> die() never returns, the break is unreachable in arch/arm64/kernel/traps.c

Is the break causing some problem, e.g. a compiler warning?

If not, then I don't see a reason to remove the break.

There are many other instances of "die(...); break" throughout the
kernel, and this doesn't seem to be speecial.

Mark.

> Signed-off-by: Osama Abdelkader <osama.abdelkader@gmail.com>
> ---
>  arch/arm64/kernel/traps.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/arch/arm64/kernel/traps.c b/arch/arm64/kernel/traps.c
> index 681939ef5d16..81dd2d7759eb 100644
> --- a/arch/arm64/kernel/traps.c
> +++ b/arch/arm64/kernel/traps.c
> @@ -1003,7 +1003,6 @@ int bug_brk_handler(struct pt_regs *regs, unsigned long esr)
>  	switch (report_bug(regs->pc, regs)) {
>  	case BUG_TRAP_TYPE_BUG:
>  		die("Oops - BUG", regs, esr);
> -		break;
>  
>  	case BUG_TRAP_TYPE_WARN:
>  		break;
> -- 
> 2.43.0
> 


  reply	other threads:[~2025-11-27  9:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26 22:26 [PATCH] arm64: Remove unreachable break after die Osama Abdelkader
2025-11-27  9:20 ` Mark Rutland [this message]
2025-11-28  2:31   ` Anshuman Khandual
2025-11-28 16:10     ` Osama Abdelkader
2025-11-28  2:41 ` kernel test robot

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=aSgX-br67x5Y-kBZ@J2N7QTR9R3 \
    --to=mark.rutland@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=osama.abdelkader@gmail.com \
    --cc=smostafa@google.com \
    --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