linux-kernel - Re: [PATCH] riscv: fix locking violation in page fault handler

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <mvmef5aqqlp.fsf@suse.de>
Date:   Tue, 07 May 2019 16:36:02 +0200
From:   Andreas Schwab <schwab@...e.de>
To:     Nikolay Borisov <nborisov@...e.com>
Cc:     linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] riscv: fix locking violation in page fault handler

On Mai 07 2019, Nikolay Borisov <nborisov@...e.com> wrote:

> On 7.05.19 г. 17:12 ч., Andreas Schwab wrote:
>> On Mai 07 2019, Nikolay Borisov <nborisov@...e.com> wrote:
>> 
>>> At the very least the code under
>>> no_context label could go into it's own function since it just kills the
>>> process and never returns?
>> 
>> This is not true.
>
> Be more specific, according to do_task_dead after the last __schedule is
> called the calling context is no more?

	/* Are we prepared to handle this kernel fault? */
	if (fixup_exception(regs))
		return;

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@...e.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."