linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco@dolcini.it>
To: Francesco Dolcini <francesco@dolcini.it>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Cc: linux-bluetooth@vger.kernel.org,
	"Sherry Sun" <sherry.sun@nxp.com>,
	"Johan Hedberg" <johan.hedberg@gmail.com>,
	"Neeraj Sanjay Kale" <neeraj.sanjaykale@nxp.com>,
	linux-kernel@vger.kernel.org,
	"Marcel Holtmann" <marcel@holtmann.org>,
	"Marcel Ziswiler" <marcel.ziswiler@toradex.com>,
	"Amitkumar Karwar" <amitkumar.karwar@nxp.com>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Marcel Ziswiler" <marcel@ziswiler.com>
Subject: Re: [PATCH v1 1/2] Bluetooth: btnxpuart: Fix btnxpuart_close
Date: Mon, 4 Mar 2024 17:52:15 +0100	[thread overview]
Message-ID: <20240304165215.GA11208@francesco-nb> (raw)
In-Reply-To: <ZWEG40nzRhm6oVEq@francesco-nb.int.toradex.com>

Hi Luiz,

On Fri, Nov 24, 2023 at 09:26:11PM +0100, Francesco Dolcini wrote:
> On Wed, Oct 18, 2023 at 04:55:39PM +0200, Marcel Ziswiler wrote:
> > From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
> > 
> > Unfortunately, btnxpuart_close() may trigger a BUG: scheduling while
> > atomic. Fix this by properly purging the transmit queue and freeing the
> > receive skb.
> > 
> > Fixes: 689ca16e5232 ("Bluetooth: NXP: Add protocol support for NXP Bluetooth chipsets")
> > 
> > Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
> > ---
> > This is the kernel trace this commit fixes:
> > [   29.270685] BUG: scheduling while atomic: kworker/u3:0/55/0x00000002
> 
> I just hit this bug with 6.7-rc2, I think it would be worth to
> apply this fix.

Do you need any change for having this patch (1/2) applied? Do you want this
to be re-sent without the second patch (2/2) from this series that is
maybe more controversial?

Let me know how I can help,

Thanks,
Francesco


  reply	other threads:[~2024-03-04 16:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18 14:55 [PATCH v1 0/2] Bluetooth: btnxpuart: Fixes Marcel Ziswiler
2023-10-18 14:55 ` [PATCH v1 1/2] Bluetooth: btnxpuart: Fix btnxpuart_close Marcel Ziswiler
2023-10-18 15:36   ` Neeraj sanjay kale
2023-10-18 16:23     ` Marcel Ziswiler
2023-10-19  9:41       ` Neeraj sanjay kale
2023-10-18 15:42   ` Bluetooth: btnxpuart: Fixes bluez.test.bot
2023-11-24 20:26   ` [PATCH v1 1/2] Bluetooth: btnxpuart: Fix btnxpuart_close Francesco Dolcini
2024-03-04 16:52     ` Francesco Dolcini [this message]
2024-03-04 17:34       ` Luiz Augusto von Dentz
2023-10-18 14:55 ` [PATCH v1 2/2] Bluetooth: btnxpuart: Fix nxp_setup Marcel Ziswiler
2023-10-18 15:28   ` Neeraj sanjay kale
2023-10-18 16:41     ` Marcel Ziswiler
2023-10-19  9:58       ` Neeraj sanjay kale
2024-01-17  5:18       ` Neeraj Sanjay Kale
2023-10-19 16:44   ` Paul Menzel
2023-10-20  7:56     ` Marcel Ziswiler
2023-10-20 10:39   ` Sherry Sun

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=20240304165215.GA11208@francesco-nb \
    --to=francesco@dolcini.it \
    --cc=amitkumar.karwar@nxp.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=luiz.von.dentz@intel.com \
    --cc=marcel.ziswiler@toradex.com \
    --cc=marcel@holtmann.org \
    --cc=marcel@ziswiler.com \
    --cc=neeraj.sanjaykale@nxp.com \
    --cc=sherry.sun@nxp.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).