public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Finn Thain <fthain@linux-m68k.org>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.4.y] signal/m68k: Use force_sigsegv(SIGSEGV) in fpsp040_die
Date: Wed, 22 Jan 2025 09:16:44 -0500	[thread overview]
Message-ID: <20250122085539-621c490778d361b8@stable.kernel.org> (raw)
In-Reply-To: <dd7ca3ed8cfac012d6001fe4d3e8d604@linux-m68k.org>

[ Sasha's backport helper bot ]

Hi,

The upstream commit SHA1 provided is correct: a3616a3c02722d1edb95acc7fceade242f6553ba

WARNING: Author mismatch between patch and upstream commit:
Backport author: Finn Thain<fthain@linux-m68k.org>
Commit author: Eric W. Biederman<ebiederm@xmission.com>


Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Present (exact SHA1)
6.1.y | Present (exact SHA1)
5.15.y | Present (exact SHA1)
5.10.y | Not found
5.4.y | Not found

Note: The patch differs from the upstream commit:
---
1:  a3616a3c02722 ! 1:  bf9f85b11138f signal/m68k: Use force_sigsegv(SIGSEGV) in fpsp040_die
    @@ Metadata
      ## Commit message ##
         signal/m68k: Use force_sigsegv(SIGSEGV) in fpsp040_die
     
    +    [ Upstream commit a3616a3c02722d1edb95acc7fceade242f6553ba ]
    +
         In the fpsp040 code when copyin or copyout fails call
         force_sigsegv(SIGSEGV) instead of do_exit(SIGSEGV).
     
    @@ Commit message
         Link: https://lkml.kernel.org/r/87tukghjfs.fsf_-_@disp2133
         Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
         Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
    +    Signed-off-by: Finn Thain <fthain@linux-m68k.org>
     
      ## arch/m68k/fpsp040/skeleton.S ##
     @@ arch/m68k/fpsp040/skeleton.S: in_ea:
    - 	.section .fixup,#alloc,#execinstr
    + 	.section .fixup,"ax"
      	.even
      1:
     -	jbra	fpsp040_die
     +	jbsr	fpsp040_die
     +	jbra	.Lnotkern
      
    - 	.section __ex_table,#alloc
    + 	.section __ex_table,"a"
      	.align	4
     
      ## arch/m68k/kernel/traps.c ##
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.4.y        |  Success    |  Success   |

      reply	other threads:[~2025-01-22 14:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-22  8:48 [PATCH 5.4.y] signal/m68k: Use force_sigsegv(SIGSEGV) in fpsp040_die Finn Thain
2025-01-22 14:16 ` Sasha Levin [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=20250122085539-621c490778d361b8@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=fthain@linux-m68k.org \
    --cc=stable@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