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=-6.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_GIT 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 EED5DC76195 for ; Thu, 18 Jul 2019 03:06:07 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id CA06B21850 for ; Thu, 18 Jul 2019 03:06:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1563419167; bh=rku9e+gLZXd0cXvofkio1Hv3SFZniVvGJAakdWxEiW0=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=QJ8ggtBa+QD/dEWJTZoVDT/ShvzA8KSEz0/strY/S5fW1VxrEcba6wiTsZNeuR7cl tQOlR9sENqKj+Ml130wtYUF9wv73Nwh5LOpgpDwrDLJFs7yJbyrVTqukgGFjG/Mqms yD/UdwTII9lEvhPv2MnikDTb3i+xkgqhLrkxpQzw= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390143AbfGRDGG (ORCPT ); Wed, 17 Jul 2019 23:06:06 -0400 Received: from mail.kernel.org ([198.145.29.99]:37280 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387984AbfGRDGF (ORCPT ); Wed, 17 Jul 2019 23:06:05 -0400 Received: from localhost (115.42.148.210.bf.2iij.net [210.148.42.115]) (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 1BB442173E; Thu, 18 Jul 2019 03:06:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1563419165; bh=rku9e+gLZXd0cXvofkio1Hv3SFZniVvGJAakdWxEiW0=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Ewvq96FT4GIlGrPnCFhIHFBP1voOn+iIo8j76NtXLQ614+ILJ386cdPzHdLpg3xMQ vmTAJaI81jXLgisr0QyQC8MP4P/v+uFtHUhvRzd9Kl9vMbBpL8ky8oRaOX73IteN+G ar97C1ZyGWd9TJpN2kdKZuPFhaC9aP8xp7jEVWx0= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Thomas Gleixner , Marc Zyngier Subject: [PATCH 5.1 42/54] genirq: Fix misleading synchronize_irq() documentation Date: Thu, 18 Jul 2019 12:01:37 +0900 Message-Id: <20190718030056.406978855@linuxfoundation.org> X-Mailer: git-send-email 2.22.0 In-Reply-To: <20190718030053.287374640@linuxfoundation.org> References: <20190718030053.287374640@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org From: Thomas Gleixner commit 1d21f2af8571c6a6a44e7c1911780614847b0253 upstream. The function might sleep, so it cannot be called from interrupt context. Not even with care. Signed-off-by: Thomas Gleixner Cc: Marc Zyngier Link: https://lkml.kernel.org/r/20190628111440.189241552@linutronix.de Signed-off-by: Greg Kroah-Hartman --- kernel/irq/manage.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) --- a/kernel/irq/manage.c +++ b/kernel/irq/manage.c @@ -96,7 +96,8 @@ EXPORT_SYMBOL(synchronize_hardirq); * to complete before returning. If you use this function while * holding a resource the IRQ handler may need you will deadlock. * - * This function may be called - with care - from IRQ context. + * Can only be called from preemptible code as it might sleep when + * an interrupt thread is associated to @irq. */ void synchronize_irq(unsigned int irq) {