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: <ae3297cc-8a8d-a48e-159e-741c7af41cf7@suse.com>
Date:   Tue, 7 May 2019 17:22:08 +0300
From:   Nikolay Borisov <nborisov@...e.com>
To:     Andreas Schwab <schwab@...e.de>,
        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 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?
> 
> Andreas.
>