Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp3381635pxf; Mon, 22 Mar 2021 05:15:01 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxlNXQmBJLexfICgpAGF/aRygfS1gwdo81bND5IwpRt2wIGhCMqDGEQl6+EIh9XgA3vtxNk X-Received: by 2002:a50:f38f:: with SMTP id g15mr25031553edm.262.1616415301823; Mon, 22 Mar 2021 05:15:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616415301; cv=none; d=google.com; s=arc-20160816; b=wrOzxLwhenOSIUlgoYGLs+lGSP4Bb17U1jmqPvoYbjh8eCy/Sk1s/6KnjwBxzlNgUX 2leJmUe0/Kwj+8aNdT+uFz+sy3rg1XchA/6yk4FxD8SbtnovL1RHQ1cwXYlOzQArbQZ8 ofZOWdimbZuVqNFmf7Foj/QoziyVYu9bgzxXJTzzwpFQzAVyOBcwl6XFLrUB1JJKuZd2 3RKgmwtLGi7Cww+PmjebFqGPCKeGLpxxqv116YD1LTG9cUpOgnI6Dn4g0UGXaCo5/VIO 32V5p3zyARLFBb1LHZzRD3k/jHjT7i9AavxcAAeAmfMoDFaqGFH8bm0uU0bK1VlU117c QVWA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:references:message-id :in-reply-to:subject:cc:to:from:date:dkim-signature; bh=lxMARE5DxBfsWWfGwrTD6C/J8Fn/PFcSw9F8CysBr8k=; b=1DxJX5+sY1Lno+PFwf7JVMt09mjxYKcLCB++dft/HGqZ/16lp+JYt28vJQkKTEvK0A KQj2dzfF3Qi8V8Z61vZIJxQcsUEjoWOrn0cw0l2NdqN20MDa+zjiVENl1Q5ptGqgtXJH goymQaCiNHIwuHeUFcZKPYzYMJgXuS4cuN/tGe9sbHp+gLYO+qiMxw2kv+pPjlCcxGES 2z5gU1LdJLWXfzWBYQW71nt0IhjJMRUg5nTOXItdTc8kH4yMkEABOKslfC2Qfap1Jt1N iIc2wrng9jBvgLF1uGF/ob1neiZfix0RUZTQriEmqznXjbONjgxjS4qgKBQKUdUqzGEt jjiA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=KcKOq3hn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id lo11si11688067ejb.60.2021.03.22.05.14.38; Mon, 22 Mar 2021 05:15:01 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=KcKOq3hn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230160AbhCVMNT (ORCPT + 99 others); Mon, 22 Mar 2021 08:13:19 -0400 Received: from mail.kernel.org ([198.145.29.99]:48570 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230258AbhCVMMz (ORCPT ); Mon, 22 Mar 2021 08:12:55 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id A62FF6196F; Mon, 22 Mar 2021 12:12:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1616415174; bh=nJ6Y0t09uPWWuWf7AN+eLehX+a2M1PUYG+ikHrZ1keM=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=KcKOq3hnx1wa45MK4b7+gfmZU/FDeRoithsKVCA3AAH9xDis0Ns2cZ9gPb6Fq76IJ M+QzWVsLqyrfw0kPho8eP1kYzSUgYk0Ji5w2KP4AfVmxy0b1tZMKDGzpsYK4XcxFD4 yt4EVuL4wnvRsNo7reD91k5GSHEpFMQ2VDlwmrZ7LdFVqKZnD9NEmWqubGWQhJxOne dRmoL7Jw7ZzEEn/3RqCDkN7tRUllAy9yY8Ww9TH8WfzdfQgHJ2W8emNFZiWcNWKNyF J8b3BdvbNl+K7/sqCwmTjNmRg2vHlOoA6epI4NAEkihFuPhTjOA9TaOGt1jFpCfPum s1Qv0seAMiXUA== Date: Mon, 22 Mar 2021 13:12:51 +0100 (CET) From: Jiri Kosina To: Luca Coelho cc: Kalle Valo , Johannes Berg , Emmanuel Grumbach , linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_enqueue_hcmd() In-Reply-To: Message-ID: References: <87h7lfbowr.fsf@tynnyri.adurom.net> <87zgz7t246.fsf@codeaurora.org> User-Agent: Alpine 2.21 (LSU 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 13 Mar 2021, Luca Coelho wrote: > > > > > > > > It's possible for iwl_pcie_enqueue_hcmd() to be called with hard IRQs > > > > > > > > disabled (e.g. from LED core). We can't enable BHs in such a situation. > > > > > > > > > > > > > > > > Turn the unconditional BH-enable/BH-disable code into > > > > > > > > hardirq-disable/conditional-enable. > > > > > > > > > > > > > > > > This fixes the warning below. > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > friendly ping on this one ... > > > > > > > > > > > > Luca, > > > > > > > > > > > > Johannes is telling me that he merged this patch internally, but I have no > > > > > > idea what is happening to it ... ? > > > > > > > > > > > > The reported splat is a clear bug, so it should be fixed one way or the > > > > > > other. > > > > > > > > > > Should I take this to wireless-drivers? > > > > > > > > I can't speak for the maintainers, but as far as I am concerned, it > > > > definitely is a 5.12 material, as it fixes real scheduling bug. > > > > > > Yes, please take this to w-d. We have a similar patch internally, but > > > there's a backlog and it will take me some time to get to it. I'll > > > resolve eventual conflicts when time comes. > > > > Ok, can I have your ack for patchwork? > > Sorry, forgot that. > > Acked-by: Luca Coelho Sorry for sounding like broken record :) but this fix is still not in any tree as far as I can tell. And it's fixing real scheduling in atomic bug. Thanks, -- Jiri Kosina SUSE Labs