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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 6B648C4332F for ; Fri, 9 Dec 2022 19:54:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:Message-ID:Date:References :In-Reply-To:Subject:Cc:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=gWph8UHFOZT9H3IWkIjRuit5ymIYz5dRJ8ToP4FsakQ=; b=helr8JfnDQM8WK ZmCRO0B5SdLMWRzP3KH465jAvpRyLvSdMIgTBJiBIZcSsbx6U0rAGDVkGI5iPvFPylhyEG6fIN+g4 gwBtD8AvLFfc5Mb9V2tJEj5JIlPgrnERtCIrWEnT7O56ac1EoVUqMCtOazyp3oncHVOyG29bh1rLL dnzRtEnhG/zXsQqM6btY/m8ndUqcbuL29Jkw2hkOFPSg4KQxa+V6ncQl4v7e0Ip8dp2FAp6S59GIQ htwUwRjwDGkOCRVveVdb/5ejpcPWX0QUVJgh32kqaoT2RYge8g0vRhuZm30DvbcQECVGdolPUMCmj sfMGjUCWePWda589dUYQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1p3jRD-00AwT2-7T; Fri, 09 Dec 2022 19:53:39 +0000 Received: from galois.linutronix.de ([2a0a:51c0:0:12e:550::1]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1p3jRA-00AwNd-Ia for linux-arm-kernel@lists.infradead.org; Fri, 09 Dec 2022 19:53:37 +0000 From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1670615608; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=2vgxfx/i9kYzvSYspcEHbEEAe0+JN+WukTrnXgbW7wY=; b=XKzurZMWPYfNQs5p8r67n9C0fgxSEHaIAiIYu/Pm1lg48sdwqnhkn7Y2m3GuOimHVqKjrT ExmvtetajHnYz97oVeQAOvkw3z1eae3xJ8sx9j70aX09BNoxePCV8udcvC7y+vIIUakS36 OWtUNrj6pdrnhfqkkPTX+snB/fsYiNOIUw5Mmbnk1m46riCRmHpPtHf0xLZTf/3kafxUqf YrXJBT47POQZw2h3PdydAVknVXAzL0VBZkyMjrGwJjeVCzaNxHzE7Qr8YQlRCM59LRO5lt Lix9aNxms4sEB1lbL3qh5NstHDLK5l0TMpwN3f9bKZKbdfy95YTcsus4A0WW1Q== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1670615608; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=2vgxfx/i9kYzvSYspcEHbEEAe0+JN+WukTrnXgbW7wY=; b=LCJeDN4TmIQw3S7soch4Gm6FTqCBtP4eFmM6foQtsFJOjidIKlDvmHtRnJ887106JJAxya XIbQS2UyZJnBAuBQ== To: Johan Hovold Cc: Johan Hovold , Marc Zyngier , x86@kernel.org, platform-driver-x86@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 00/19] irqdomain: fix mapping race and clean up locking In-Reply-To: References: <20221209140150.1453-1-johan+linaro@kernel.org> <87o7scd197.ffs@tglx> Date: Fri, 09 Dec 2022 20:53:28 +0100 Message-ID: <87lengcq13.ffs@tglx> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221209_115336_783730_CC64CFCF X-CRM114-Status: GOOD ( 15.85 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, Dec 09 2022 at 17:16, Johan Hovold wrote: > On Fri, Dec 09, 2022 at 04:51:00PM +0100, Thomas Gleixner wrote: >> On Fri, Dec 09 2022 at 15:01, Johan Hovold wrote: >> > Parallel probing (e.g. due to asynchronous probing) of devices that >> > share interrupts can currently result in two mappings for the same >> > hardware interrupt to be created. >> > >> > This series fixes this mapping race and clean up the irqdomain locking >> > so that in the end the global irq_domain_mutex is only used for managing >> > the likewise global irq_domain_list, while domain operations (e.g. >> > IRQ allocations) use per-domain (hierarchy) locking. >> >> Can you please rebase that on top of: >> >> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq/core > > The series is based on next-20221208 which should contain that branch in > its current state if I'm not mistaken. > > I just tried applying it on top of irq/core and did not notice any > problems. Sorry for the noise. Pilot error. -ETOOMANYBRANCHES :) _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel