linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-arch@vger.kernel.org, linux-parisc@vger.kernel.org
Subject: Re: [PATCH 08/10] parisc: fix livelock in uaccess
Date: Tue, 28 Feb 2023 19:26:48 +0100	[thread overview]
Message-ID: <e9972a0e-14e6-987c-fcee-005a50d28e46@gmx.de> (raw)
In-Reply-To: <Y/47PMmpLDX5lPWx@ZenIV>

On 2/28/23 18:34, Al Viro wrote:
> On Mon, Feb 06, 2023 at 05:58:02PM +0100, Helge Deller wrote:
>> Hi Al,
>>
>> On 1/31/23 21:06, Al Viro wrote:
>>> parisc equivalent of 26178ec11ef3 "x86: mm: consolidate VM_FAULT_RETRY handling"
>>> If e.g. get_user() triggers a page fault and a fatal signal is caught, we might
>>> end up with handle_mm_fault() returning VM_FAULT_RETRY and not doing anything
>>> to page tables.  In such case we must *not* return to the faulting insn -
>>> that would repeat the entire thing without making any progress; what we need
>>> instead is to treat that as failed (user) memory access.
>>>
>>> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
>>> ---
>>>    arch/parisc/mm/fault.c | 5 ++++-
>>>    1 file changed, 4 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/arch/parisc/mm/fault.c b/arch/parisc/mm/fault.c
>>> index 869204e97ec9..bb30ff6a3e19 100644
>>> --- a/arch/parisc/mm/fault.c
>>> +++ b/arch/parisc/mm/fault.c
>>> @@ -308,8 +308,11 @@ void do_page_fault(struct pt_regs *regs, unsigned long code,
>>>
>>>    	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;
>>> +	}
>>
>> The testcase in
>>    https://lore.kernel.org/lkml/20170822102527.GA14671@leverpostej/
>>    https://lore.kernel.org/linux-arch/20210121123140.GD48431@C02TD0UTHF1T.local/
>> does hang with and without above patch on parisc.
>> It does not consume CPU in that state and can be killed with ^C.
>>
>> Any idea?
>
> 	Still trying to resurrect the parisc box to test on it...
> FWIW, right now I've locally confirmed that mainline has the bug
> in question and that patch fixes it for alpha, sparc32 and sparc64;
> hexagon, m68k and riscv got acks from other folks; microblaze,
> nios2 and openrisc I can't test at all (no hardware, no qemu setup);
> same for parisc64.  Itanic and parisc32 I might be able to test,
> if I manage to resurrect the hardware.

I can test both parisc32 and parisc64.

> 	Just to confirm: your "can be killed with ^C" had been on the
> mainline parisc kernel (with userfaultfd enable, of course, or it wouldn't
> hang up at all), right?

It was a recent mainline kernel with your patch.

> Was it 32bit or 64bit kernel?

I don't remember. I think I tried both.

Helge

  reply	other threads:[~2023-02-28 18:27 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 20:02 [RFC][PATCHSET] VM_FAULT_RETRY fixes Al Viro
2023-01-31 20:03 ` [PATCH 01/10] alpha: fix livelock in uaccess Al Viro
2023-03-07  0:48   ` patchwork-bot+linux-riscv
2023-01-31 20:03 ` [PATCH 02/10] hexagon: " Al Viro
2023-02-10  2:59   ` Brian Cain
2023-01-31 20:04 ` [PATCH 03/10] ia64: " Al Viro
2023-01-31 20:04 ` [PATCH 04/10] m68k: " Al Viro
2023-02-05  6:18   ` Finn Thain
2023-02-05 18:51     ` Linus Torvalds
2023-02-07  3:07       ` Finn Thain
2023-02-05 20:39     ` Al Viro
2023-02-05 20:41       ` Linus Torvalds
2023-02-06 12:08   ` Geert Uytterhoeven
2023-01-31 20:05 ` [PATCH 05/10] microblaze: " Al Viro
2023-01-31 20:05 ` [PATCH 06/10] nios2: " Al Viro
2023-01-31 20:06 ` [PATCH 07/10] openrisc: " Al Viro
2023-01-31 20:06 ` [PATCH 08/10] parisc: " Al Viro
2023-02-06 16:58   ` Helge Deller
2023-02-28 17:34     ` Al Viro
2023-02-28 18:26       ` Helge Deller [this message]
2023-02-28 19:14         ` Al Viro
2023-02-28 19:32           ` Helge Deller
2023-02-28 20:00             ` Helge Deller
2023-02-28 20:22               ` Helge Deller
2023-02-28 22:57                 ` Al Viro
2023-03-01  4:00                   ` Helge Deller
2023-03-02 17:53                     ` Al Viro
2023-02-28 15:22   ` Guenter Roeck
2023-02-28 19:18     ` Michael Schmitz
2023-01-31 20:06 ` [PATCH 09/10] riscv: " Al Viro
2023-02-06 20:06   ` Björn Töpel
2023-02-07 16:11   ` Geert Uytterhoeven
2023-01-31 20:07 ` [PATCH 10/10] sparc: " Al Viro
2023-01-31 20:24 ` [RFC][PATCHSET] VM_FAULT_RETRY fixes Linus Torvalds
2023-01-31 21:10   ` Al Viro
2023-01-31 21:19     ` Linus Torvalds
2023-01-31 21:49       ` Al Viro
2023-02-01  0:00         ` Linus Torvalds
2023-02-01 19:48           ` Peter Xu
2023-02-01 22:18             ` Al Viro
2023-02-02  0:57               ` Al Viro
2023-02-02 22:56               ` Peter Xu
2023-02-04  0:26                 ` Al Viro
2023-02-05  5:10                   ` Al Viro
2023-02-04  0:47         ` [loongarch oddities] " Al Viro
2023-02-01  8:21       ` Helge Deller
2023-02-01 19:51         ` Linus Torvalds
2023-02-02  6:58       ` Al Viro
2023-02-02  8:54         ` Michael Cree
2023-02-02  9:56           ` John Paul Adrian Glaubitz
2023-02-02 15:20           ` Al Viro
2023-02-02 20:20             ` Al Viro
2023-02-02 20:34         ` Linus Torvalds
2023-02-01 10:50 ` Mark Rutland
2023-02-06 12:08   ` Geert Uytterhoeven

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=e9972a0e-14e6-987c-fcee-005a50d28e46@gmx.de \
    --to=deller@gmx.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).