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.3 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no 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 89912C74A4B for ; Thu, 11 Jul 2019 09:58:34 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 0FE6B20645 for ; Thu, 11 Jul 2019 09:58:33 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="SIh85Idm" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0FE6B20645 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from lists.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 45ks2H4hy0zDqLc for ; Thu, 11 Jul 2019 19:58:31 +1000 (AEST) Authentication-Results: lists.ozlabs.org; spf=pass (mailfrom) smtp.mailfrom=gmail.com (client-ip=2607:f8b0:4864:20::531; helo=mail-pg1-x531.google.com; envelope-from=npiggin@gmail.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="SIh85Idm"; dkim-atps=neutral Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 45krzP3MyTzDq77 for ; Thu, 11 Jul 2019 19:56:01 +1000 (AEST) Received: by mail-pg1-x531.google.com with SMTP id q4so2683052pgj.8 for ; Thu, 11 Jul 2019 02:56:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:subject:to:cc:references:in-reply-to:mime-version :user-agent:message-id:content-transfer-encoding; bh=q4aTVXnmJvx0+ZI6UEfBVpgkZHcZDIxsB4G/ZiMf9pM=; b=SIh85Idmmnmu84Er31UhNLbVafgqi0UkV82OpvVm7rtrxdNqU0AhgtRNEDYXqq1Rnd ugoF2aZF4eWlgQOGXYnlVOibsauiHFEV10Ne5Io7r7KiKdqT4/Zbq/e97dKABlp2y/JK rim13rddkbLQIxqq6Ue2WPkqomeZg+m1Umlth521X+2g4GgLgREy/079n7cdVwiRR8kE CP+XnaBtURhybFsdjMQjhtImN2cnppq3JBkuHelKJSc0HRvYBnYEg6DBuEMzbtug3iS0 SCZ8IVEyQcU3kuZdSkRE9cPSfELrqMZY3JoiNNYaRHuJ0Sil5qisb5/bBUcP7Bwi6jBD FNWw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:subject:to:cc:references:in-reply-to :mime-version:user-agent:message-id:content-transfer-encoding; bh=q4aTVXnmJvx0+ZI6UEfBVpgkZHcZDIxsB4G/ZiMf9pM=; b=hwKibFK/zubneX8CIRDHxZ7fCAJKsjJr6uqb68v1GBExQVebq70pYx+CX8W0+2Vaf7 EnVvBINjTtKzhwA6nPHvhs4JdvlIq9ff1IIAXHvJqStgCVdZKGF/qxPAkVNkKpzT3emh cXXgu+bWgGQGYuNzyTRZFpH+lNDaPQxRxbxRFtPsrx+K9jJKf3NKs06PjP+twQbvHVEC LLRGo+6syKUUx3FRNV+fuv/rhI+wQIZiRUM49mpIRL0wTEUbR+iOPmdKOu74dOD0zQNh ZTcx7+DE4zGHhRQ3MgappRQNNFykill5KODgyB3vRtITR+xPFzxh5lbaAdwRKk8mjrep 2Jnw== X-Gm-Message-State: APjAAAX8osJj+WZkNRG/VhcmdOXFiszls8aZKbG0BB/KvdKlUMjqqq1m d6aBCTD8DYVLhHGgu407+RQ= X-Google-Smtp-Source: APXvYqwvy8CZPo/ZKAxkPcg+J1VB346XgSM3stuTnmFgdJfcOxtjIO4tApyo1mgLo+tzQKgwBPC0UA== X-Received: by 2002:a63:181:: with SMTP id 123mr3550274pgb.63.1562838958158; Thu, 11 Jul 2019 02:55:58 -0700 (PDT) Received: from localhost (193-116-118-149.tpgi.com.au. [193.116.118.149]) by smtp.gmail.com with ESMTPSA id f3sm6828140pfg.165.2019.07.11.02.55.56 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Thu, 11 Jul 2019 02:55:57 -0700 (PDT) Date: Thu, 11 Jul 2019 19:52:59 +1000 From: Nicholas Piggin Subject: Re: [v5 5/6] powerpc/mce: Handle UE event for memcpy_mcsafe To: linux-kernel@vger.kernel.org, linuxppc-dev , Santosh Sivaraj References: <20190709121524.18762-1-santosh@fossix.org> <20190709121524.18762-6-santosh@fossix.org> In-Reply-To: <20190709121524.18762-6-santosh@fossix.org> MIME-Version: 1.0 User-Agent: astroid/0.14.0 (https://github.com/astroidmail/astroid) Message-Id: <1562838616.xzrha67fy6.astroid@bobo.none> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "Aneesh Kumar K.V" , Mahesh Salgaonkar , Chandan Rajendra , Reza Arbab Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" Santosh Sivaraj's on July 9, 2019 10:15 pm: > If we take a UE on one of the instructions with a fixup entry, set nip > to continue execution at the fixup entry. Stop processing the event > further or print it. So... what happens if we take a machine check while we happen to be executing some other kernel operation with a fixup entry? Or the other way around, what happens if memcpy_mcsafe takes a page fault for some reason (e.g., kernel bug it tries to access unmapped memory). Thanks, Nick =