From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B878AC004C9 for ; Tue, 7 May 2019 14:36:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8DAF420989 for ; Tue, 7 May 2019 14:36:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726653AbfEGOgE (ORCPT ); Tue, 7 May 2019 10:36:04 -0400 Received: from mx2.suse.de ([195.135.220.15]:51874 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726403AbfEGOgD (ORCPT ); Tue, 7 May 2019 10:36:03 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id C26BDAD55; Tue, 7 May 2019 14:36:02 +0000 (UTC) From: Andreas Schwab To: Nikolay Borisov Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] riscv: fix locking violation in page fault handler References: X-Yow: I'm RELIGIOUS!! I love a man with a HAIRPIECE!! Equip me with MISSILES!! Date: Tue, 07 May 2019 16:36:02 +0200 In-Reply-To: (Nikolay Borisov's message of "Tue, 7 May 2019 17:22:08 +0300") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mai 07 2019, Nikolay Borisov wrote: > On 7.05.19 г. 17:12 ч., Andreas Schwab wrote: >> On Mai 07 2019, Nikolay Borisov 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@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."