From: Mark Rutland <mark.rutland@arm.com>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: mm: abort uaccess retries upon fatal signal
Date: Fri, 22 Jan 2021 10:11:57 +0000 [thread overview]
Message-ID: <20210122101157.GB29124@C02TD0UTHF1T.local> (raw)
In-Reply-To: <20210121160416.111298-1-tsbogend@alpha.franken.de>
On Thu, Jan 21, 2021 at 05:04:16PM +0100, Thomas Bogendoerfer wrote:
> When there's a fatal signal pending, MIPS's do_page_fault()
> implementation returns. The intent is that we'll return to the
> faulting userspace instruction, delivering the signal on the way.
>
> However, if we take a fatal signal during fixing up a uaccess, this
> results in a return to the faulting kernel instruction, which will be
> instantly retried, resulting in the same fault being taken forever. As
> the task never reaches userspace, the signal is not delivered, and the
> task is left unkillable. While the task is stuck in this state, it can
> inhibit the forward progress of the system.
>
> To avoid this, we must ensure that when a fatal signal is pending, we
> apply any necessary fixup for a faulting kernel instruction. Thus we
> will return to an error path, and it is up to that code to make forward
> progress towards delivering the fatal signal.
>
> [ Description taken from commit 746a272e4414 ("ARM: 8692/1: mm: abort
> uaccess retries upon fatal signal") ]
>
> Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
FWIW, this looks right to me, from a scan of the no_context path. I
don't have any MIPS system to test on, but FWIW:
Acked-by: Mark Rutland <mark.rutland@arm.com>
Thanks for spinning this!
Mark.
> ---
> arch/mips/mm/fault.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/arch/mips/mm/fault.c b/arch/mips/mm/fault.c
> index 7c871b14e74a..e7abda9c013f 100644
> --- a/arch/mips/mm/fault.c
> +++ b/arch/mips/mm/fault.c
> @@ -156,8 +156,11 @@ static void __kprobes __do_page_fault(struct pt_regs *regs, unsigned long write,
> */
> fault = handle_mm_fault(vma, address, flags, regs);
>
> - if (fault_signal_pending(fault, regs))
> + if (fault_signal_pending(fault, regs)) {
> + if (!user_mode(regs))
> + goto no_context;
> return;
> + }
>
> if (unlikely(fault & VM_FAULT_ERROR)) {
> if (fault & VM_FAULT_OOM)
> --
> 2.29.2
>
next prev parent reply other threads:[~2021-01-22 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 16:04 Thomas Bogendoerfer
2021-01-22 10:11 ` Mark Rutland [this message]
2021-01-22 10:28 ` Thomas Bogendoerfer
2021-01-22 10:49 ` Thomas Bogendoerfer
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=20210122101157.GB29124@C02TD0UTHF1T.local \
--to=mark.rutland@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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®