Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp1907155imm; Thu, 24 May 2018 02:43:09 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoozsbRHycjBWPi79LE+XCeld4sVaGJrXYXhwrTIo0Hc7CItlSUESGTxYM3WxOd+nz5xJ+w X-Received: by 2002:a63:18a:: with SMTP id 132-v6mr5360990pgb.344.1527154989253; Thu, 24 May 2018 02:43:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527154989; cv=none; d=google.com; s=arc-20160816; b=swgzbP4kdpUvp35pCBnZFfg/hh+IUuAsNz6KjtT4E66v3bNo0dH+QWWcA5nB+PZebn PIwQr3mj6KiBEGf8cLEKOI5sydeeHsG+dMstLYsqAtC7JT4nsSGxV/tkY4WyJzwBbCEK pPyAZJBaIFCLhEieqkioRZRZMZAXDqfZbfZbEKPLwCv1scd+zOaYEQPzPPJyPx4LRbr/ NUEz2Y04L26bIQVNAH9lJ1IMsJioz7iNwdxUlbLMDPtZTzkze54m2cnCvjYQIw0wJHpP ncDA1S/P/Jjh6bMcL8ZfCBRx7v462w4ta4DKBas2aBGOlrJ/c841HMKrcUKBvMveylJL YyJw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :in-reply-to:message-id:date:subject:cc:to:from:dkim-signature :arc-authentication-results; bh=DmlA/L+yBnLoYgoHTqSEbRKnxpbRbVY8CKlDd9IXNLc=; b=mBrrulAgXC2ZYhoQc/BABxr4OHLkyosvf6Ngj+yBDY4kgneFFEJSGLFw82gU/hHMiN EtalzV8QPJgAKiMUE5Iyangp32/BkIyrZiuNjOlW0QP5PlqqjIS5njc5paLVMBkdEDQH 895laoTtb4WNWxlXWCWb04cWLziIBAhyxAMCj2rH8a8zTLzYpMTg3xroXvtuFLu6pRuG Fg4mpyNA3E/fo162UfYI16HZkOnx6Cz+1GhkuxKycgsIVF+iKuH9s7Ex1SaYxQZryeQG GZvF8wTQAtw3zpNWxpBx/LaHXN59xjCE5pjkmnruqbpSxa/jGiFRafE3jB45F6N3PGCT 6vtQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=o8mWpKKE; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e184-v6si16701353pgc.475.2018.05.24.02.42.54; Thu, 24 May 2018 02:43:09 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=o8mWpKKE; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966277AbeEXJmB (ORCPT + 99 others); Thu, 24 May 2018 05:42:01 -0400 Received: from mail.kernel.org ([198.145.29.99]:53652 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966025AbeEXJlx (ORCPT ); Thu, 24 May 2018 05:41:53 -0400 Received: from localhost (LFbn-1-12247-202.w90-92.abo.wanadoo.fr [90.92.61.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 5A80820893; Thu, 24 May 2018 09:41:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1527154912; bh=7+Wx8rDb9bsD65RPd1Z85wIxHYUvAd5B+aRtUsq0sYg=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=o8mWpKKEtqWkQI6ClU/VhEe/elygwVYlYXS4XfkuailEJbEr4B5DYhFeZi6nAO0LY +wIa5l49fBraqkcUIpso9JQbQXayT19auEuWVk843lJZnmnWixaiBzcI32Dlx15i+p XELFvhTtPFqv5rWRHq7yADi7GNNHHXjNnyJfzkDQ= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Nicholas Piggin , Michael Ellerman Subject: [PATCH 3.18 33/45] powerpc/powernv: Fix NVRAM sleep in invalid context when crashing Date: Thu, 24 May 2018 11:38:41 +0200 Message-Id: <20180524093124.842743719@linuxfoundation.org> X-Mailer: git-send-email 2.17.0 In-Reply-To: <20180524093120.599252450@linuxfoundation.org> References: <20180524093120.599252450@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 3.18-stable review patch. If anyone has any objections, please let me know. ------------------ From: Nicholas Piggin commit c1d2a31397ec51f0370f6bd17b19b39152c263cb upstream. Similarly to opal_event_shutdown, opal_nvram_write can be called in the crash path with irqs disabled. Special case the delay to avoid sleeping in invalid context. Fixes: 3b8070335f75 ("powerpc/powernv: Fix OPAL NVRAM driver OPAL_BUSY loops") Cc: stable@vger.kernel.org # v3.2 Signed-off-by: Nicholas Piggin Signed-off-by: Michael Ellerman Signed-off-by: Greg Kroah-Hartman --- arch/powerpc/platforms/powernv/opal-nvram.c | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) --- a/arch/powerpc/platforms/powernv/opal-nvram.c +++ b/arch/powerpc/platforms/powernv/opal-nvram.c @@ -43,6 +43,10 @@ static ssize_t opal_nvram_read(char *buf return count; } +/* + * This can be called in the panic path with interrupts off, so use + * mdelay in that case. + */ static ssize_t opal_nvram_write(char *buf, size_t count, loff_t *index) { s64 rc = OPAL_BUSY; @@ -57,10 +61,16 @@ static ssize_t opal_nvram_write(char *bu while (rc == OPAL_BUSY || rc == OPAL_BUSY_EVENT) { rc = opal_write_nvram(__pa(buf), count, off); if (rc == OPAL_BUSY_EVENT) { - msleep(OPAL_BUSY_DELAY_MS); + if (in_interrupt() || irqs_disabled()) + mdelay(OPAL_BUSY_DELAY_MS); + else + msleep(OPAL_BUSY_DELAY_MS); opal_poll_events(NULL); } else if (rc == OPAL_BUSY) { - msleep(OPAL_BUSY_DELAY_MS); + if (in_interrupt() || irqs_disabled()) + mdelay(OPAL_BUSY_DELAY_MS); + else + msleep(OPAL_BUSY_DELAY_MS); } }