From: Michael Schmitz <schmitzmic@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, uli@fpond.eu, fthain@linux-m68k.org,
viro@zeniv.linux.org.uk
Subject: Re: [PATCH RFC v2 4/8] m68k: Handle arrivals of multiple signals correctly
Date: Mon, 5 Feb 2024 23:15:48 +1300 [thread overview]
Message-ID: <401b6911-e6ed-3e9f-9dcc-d4f951c6beef@gmail.com> (raw)
In-Reply-To: <CAMuHMdUMwQSEwDQ3tsmChutY3P0VQUA0A8jg63NxfyrmxfKWXQ@mail.gmail.com>
Hi Geert,
thanks for your feedback!
Am 05.02.2024 um 21:10 schrieb Geert Uytterhoeven:
> Hi Michael,
>
> Thanks for your patch!
>
> On Mon, Feb 5, 2024 at 3:32 AM Michael Schmitz <schmitzmic@gmail.com> wrote:
>> From: Al Viro <viro@zeniv.linux.org.uk>
>
> When submitting a backport, please add lines like
>
> commit 4bb0bd81ce5e97092dfda6a106d414b703ec0ee8 upstream.
Will do. I did wonder how the original commit could be found to prevent
duplicates...
On that note - Uli: would you prefer the entire backport series, or only
those you do not already have?
>> When we have several pending signals, have entered with the kernel
>> with large exception frame *and* have already built at least one
>> sigframe, regs->stkadj is going to be non-zero and regs->format/sr/pc
>> are going to be junk - the real values are in shifted exception stack
>> frame we'd built when putting together the first sigframe.
>>
>> If that happens, subsequent sigframes are going to be garbage.
>> Not hard to fix - just need to find the "adjusted" frame first
>> and look for format/vector/sr/pc in it.
>>
>> MSch: Minor v4.4 backport merge conflict fixes.
>
> Please move this to "[MSch: ...] below...
>
>>
>> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
>> Tested-by: Michael Schmitz <schmitzmic@gmail.com>
>> Reviewed-by: Michael Schmitz <schmitzmic@gmail.com>
>> Tested-by: Finn Thain <fthain@linux-m68k.org>
>> Link: https://lore.kernel.org/r/YP2dBIAPTaVvHiZ6@zeniv-ca.linux.org.uk
>> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
>
> ... i.e. here.
OK.
>
>> Signed-off-by: Michael Schmitz <schmitzmic@gmail.com>
>
> Good.
> Please add your SoB on all patches you handle, some lack it.
That would have been the ones that did not need any extra handling. But
I take your point ...
> Thanks a lot for taking care of this!
No matter!
Cheers,
Michael
>
> Gr{oetje,eeting}s,
>
> Geert
>
next prev parent reply other threads:[~2024-02-05 10:15 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 [this message]
2024-02-08 11:53 ` Ulrich Hecht
2024-02-08 22:51 ` Finn Thain
2024-02-12 0:48 ` Michael Schmitz
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=401b6911-e6ed-3e9f-9dcc-d4f951c6beef@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