From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/2] shared: mainloop: Skip removed mainloop events
Date: Mon, 28 Sep 2026 17:50:11 +0000 [thread overview]
Message-ID: <179061781113.50268.815655039941498260.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <fc1baff935104e08b170f528477e31bfedc57c7c.1790531371.git.pav@iki.fi>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 27 Sep 2026 20:49:49 +0300 you wrote:
> mainloop_remove_fd() on an fd that occurs in the same epoll_wait batch
> as the current callback, causes ASan crash.
>
> Several callsites do this, crash is sporadic since it requires suitable
> timing.
>
> Fix by adding registration ID in each event and dispatching only if that
> registration is still active.
>
> [...]
Here is the summary with links:
- [BlueZ,1/2] shared: mainloop: Skip removed mainloop events
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c2ef55e49f2b
- [BlueZ,2/2] unit: test-mainloop: add basic mainloop test
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=45c3b69db034
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-28 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 17:49 [PATCH BlueZ 1/2] shared: mainloop: Skip removed mainloop events Pauli Virtanen
2026-09-27 17:49 ` [PATCH BlueZ 2/2] unit: test-mainloop: add basic mainloop test Pauli Virtanen
2026-09-27 21:14 ` [BlueZ,1/2] shared: mainloop: Skip removed mainloop events bluez.test.bot
2026-09-28 17:50 ` patchwork-bot+bluetooth [this message]
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=179061781113.50268.815655039941498260.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.