linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Jiri Kosina <jikos@kernel.org>, Luca Coelho <luciano.coelho@intel.com>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Lockdep warning in iwl_pcie_rx_handle()
Date: Mon, 01 Mar 2021 22:12:21 +0100	[thread overview]
Message-ID: <2db8f779b4b37d4498cfeaed77d5ede54e429a6e.camel@sipsolutions.net> (raw)
In-Reply-To: <nycvar.YFH.7.76.2103012136570.12405@cbobk.fhfr.pm> (sfid-20210301_215846_256695_15E0D07E)

Hi Jiri,

> I am getting the splat below with Linus' tree as of today (5.11-rc1, 
> fe07bfda2fb). I haven't started to look into the code yet, but apparently 
> this has been already reported by Heiner here:
> 
> 	https://www.spinics.net/lists/linux-wireless/msg208353.html
> 
> so before I start digging deep into it (the previous kernel this 
> particular machine had is 5.9, so I'd rather avoid lenghty bisect for now 
> in case someone has already looked into it and has ideas where the problem 
> is), I thought I'd ask whether this has been root-caused elsewhere 
> already.

Yeah, I'm pretty sure we have a fix for this, though I'm not sure right
now where it is in the pipeline.

It's called "iwlwifi: pcie: don't add NAPI under rxq->lock" but right
now I can't find it in any of the public archives.

johannes


  parent reply	other threads:[~2021-03-02  7:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01 20:44 Lockdep warning in iwl_pcie_rx_handle() Jiri Kosina
2021-03-01 21:09 ` Jiri Kosina
2021-03-01 21:12 ` Johannes Berg [this message]
2021-03-02  9:27   ` [PATCH] iwlwifi: don't call netif_napi_add() with rxq->lock held (was Re: Lockdep warning in iwl_pcie_rx_handle()) Jiri Kosina
2021-03-02 10:34     ` [PATCH v2] " Jiri Kosina
2021-03-02 10:49       ` Coelho, Luciano
2021-03-02 12:17         ` Kalle Valo
2021-03-02 14:55           ` Jiri Kosina
2021-03-03 21:39           ` Sedat Dilek
2021-03-03 15:59       ` Kalle Valo
     [not found]       ` <20210303155941.25521C43463@smtp.codeaurora.org>
2021-03-03 18:01         ` Jiri Kosina
2021-03-03 18:33           ` Kalle Valo
2021-03-03 19:19             ` Jiri Kosina
2021-03-02 10:48     ` [PATCH] " Coelho, Luciano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2db8f779b4b37d4498cfeaed77d5ede54e429a6e.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=hkallweit1@gmail.com \
    --cc=jikos@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luciano.coelho@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).