From: Michael Schmitz <schmitzmic@gmail.com>
To: Finn Thain <fthain@linux-m68k.org>, Ulrich Hecht <uli@fpond.eu>,
Al Viro <viro@zeniv.linux.org.uk>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>, linux-m68k@vger.kernel.org
Subject: Re: [PATCH RFC v2 4/8] m68k: Handle arrivals of multiple signals correctly
Date: Mon, 12 Feb 2024 13:48:56 +1300 [thread overview]
Message-ID: <142a53d7-3a29-4609-b3b7-07f7f00ca64f@gmail.com> (raw)
In-Reply-To: <34d37f57-3146-8aa0-7828-2df2d1679ee4@linux-m68k.org>
On 9/02/24 11:51, Finn Thain wrote:
> On Thu, 8 Feb 2024, Ulrich Hecht wrote:
>
>>> On 02/05/2024 11:15 AM CET Michael Schmitz <schmitzmic@gmail.com>
>>> wrote: On that note - Uli: would you prefer the entire backport
>>> series, or only those you do not already have?
>> I'd prefer to only get what's missing.
>>
> Ulrich, I imagine that you would normally receive fixes via the
> corresponding -stable trees. If Michael's series went into
> stable/linux-4.19.y you could cherry-pick from there for your v4.4.y tree
> and maybe avoid some merge conflicts that way. So perhaps we should ask
> the -stable maintainers to backport first (?)
>
> Al, I see that the following commits are missing from stable/linux-v6.1
> and older trees, despite the word "fix" in the subject. Reading the merge
> commit 1a8d05a726dc "Merge tag 'pull-fixes' of
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs" suggests to me
> that these are old bugs...
Only
bd75497a77cc m68k: fix livelock in uaccess, and
0d20abde987b m68k: Leave stack mangling to asm wrapper of sigreturn()
need changes to apply to v4.19. Only compile tested so far.
Happy to submit the adjusted patches to stable, and ask the stable
maintainers to pick up the missing bits from Linus' or Geert's tree.
Would that be good enough?
Cheers,
Michael
>
> bd75497a77cc m68k: fix livelock in uaccess
> d835eb3a57de riscv: fix livelock in uaccess
> 0b92ed09cb9f hexagon: fix livelock in uaccess
> 15261678a8c2 parisc: fix livelock in uaccess
> dce45493aff3 alpha: fix livelock in uaccess
> 79c54c97c773 sparc: fix livelock in uaccess
> d088af1e221c ia64: fix livelock in uaccess
> a1179ac743e8 microblaze: fix livelock in uaccess
> e902e508c5b2 nios2: fix livelock in uaccess
> caa82ae7ef52 openrisc: fix livelock in uaccess
>
> In addition, stable/linux-v5.10 and the older trees lack the following
> commit, despite the Fixes tag.
>
> 50e43a573344 m68k: Update ->thread.esp0 before calling syscall_trace() in ret_from_signal
next prev parent reply other threads:[~2024-02-12 0:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 2:32 [PATCH RFC v2 0/8] m68k v4.4 backport fixes Michael Schmitz
2024-02-05 2:32 ` [PATCH RFC v2 1/8] m68k/mm: Adjust VM area to be unmapped by gap size for __iounmap() Michael Schmitz
2024-02-05 2:32 ` [PATCH RFC v2 2/8] m68k: Only force 030 bus error if PC not in exception table Michael Schmitz
2024-02-05 2:32 ` [PATCH RFC v2 3/8] m68k: include module.h to make use of exception handling in traps.c Michael Schmitz
2024-02-05 2:32 ` [PATCH RFC v2 4/8] m68k: Handle arrivals of multiple signals correctly Michael Schmitz
2024-02-05 8:10 ` Geert Uytterhoeven
2024-02-05 10:15 ` Michael Schmitz
2024-02-08 11:53 ` Ulrich Hecht
2024-02-08 22:51 ` Finn Thain
2024-02-12 0:48 ` Michael Schmitz [this message]
2024-02-12 10:02 ` Ulrich Hecht
2024-02-13 5:05 ` Finn Thain
2024-02-05 2:32 ` [PATCH RFC v2 5/8] m68k: Update ->thread.esp0 before calling syscall_trace() in ret_from_signal Michael Schmitz
2024-02-05 2:32 ` [PATCH RFC v2 6/8] m68k: Leave stack mangling to asm wrapper of sigreturn() Michael Schmitz
2024-02-05 2:32 ` [PATCH RFC v2 7/8] m68k: fix livelock in uaccess Michael Schmitz
2024-02-05 2:32 ` [PATCH RFC v2 8/8] m68k: Move signal frame following exception on 68020/030 Michael Schmitz
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=142a53d7-3a29-4609-b3b7-07f7f00ca64f@gmail.com \
--to=schmitzmic@gmail.com \
--cc=fthain@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=uli@fpond.eu \
--cc=viro@zeniv.linux.org.uk \
/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