From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 1/4] btio: Handle EOPNOTSUPP from accept() to prevent busy loop
Date: Wed, 10 Jun 2026 18:30:06 +0000 [thread overview]
Message-ID: <178111620639.3582779.16078863116102964223.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260609185313.155105-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 9 Jun 2026 14:53:10 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> When accept() returns EOPNOTSUPP on an L2CAP SEQPACKET server socket
> (e.g. AVCTP browsing channel, PSM 0x1b), the error is permanent and
> retrying will never succeed. Previously, only EBADFD was treated as
> fatal, causing server_cb to return TRUE for EOPNOTSUPP. Since the fd
> remains readable, this creates an infinite busy loop that hangs
> bluetoothd.
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/4] btio: Handle EOPNOTSUPP from accept() to prevent busy loop
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=8c580d30d265
- [BlueZ,v2,2/4] profile: Check if bearer is enabled on registration
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=abf0911e25ef
- [BlueZ,v2,3/4] plugins: Check btd_profile_register return value
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=7b5895d80635
- [BlueZ,v2,4/4] bearer: Check btd_opts.mode on btd_bearer_new
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=8c821a150b8f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-06-10 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 18:53 [PATCH BlueZ v2 1/4] btio: Handle EOPNOTSUPP from accept() to prevent busy loop Luiz Augusto von Dentz
2026-06-09 18:53 ` [PATCH BlueZ v2 2/4] profile: Check if bearer is enabled on registration Luiz Augusto von Dentz
2026-06-09 18:53 ` [PATCH BlueZ v2 3/4] plugins: Check btd_profile_register return value Luiz Augusto von Dentz
2026-06-09 18:53 ` [PATCH BlueZ v2 4/4] bearer: Check btd_opts.mode on btd_bearer_new Luiz Augusto von Dentz
2026-06-09 21:31 ` [BlueZ,v2,1/4] btio: Handle EOPNOTSUPP from accept() to prevent busy loop bluez.test.bot
2026-06-10 18:30 ` patchwork-bot+bluetooth [this message]
2026-06-11 14:58 ` [PATCH BlueZ v2 1/4] " Bastien Nocera
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=178111620639.3582779.16078863116102964223.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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