From: patchwork-bot+bluetooth@kernel.org
To: Linmao Li <lilinmao@kylinos.cn>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: hci_core: Fix inquiry cache timestamps on 64-bit systems
Date: Tue, 22 Sep 2026 15:00:10 +0000 [thread overview]
Message-ID: <179008921025.4126096.7212004044919126524.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260922020141.389269-1-lilinmao@kylinos.cn>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 22 Sep 2026 10:01:41 +0800 you wrote:
> On 64-bit systems, outgoing BR/EDR connections always fall back to page
> scan repetition mode R2 with no clock offset once the system has been
> up for more than five minutes, even when inquiry found the peer only
> seconds earlier. This lengthens paging and can increase the risk of a
> Page Timeout.
>
> The inquiry cache stores jiffies in __u32 timestamps, but its age
> helpers subtract them from unsigned long jiffies. INITIAL_JIFFIES casts
> -300 * HZ through unsigned int, so jiffies crosses 2^32 five minutes
> after boot on 64-bit systems. Assigning it to __u32 then drops the upper
> 32 bits. In one trace, a 7.6-second-old entry (HZ=1000) was reported as
> 2^32 + 7620 ticks old and rejected by hci_acl_create_conn_sync().
> hci_inquiry() is affected by the same truncation when checking the whole
> cache. 32-bit systems are unaffected because unsigned long is 32 bits
> wide there.
>
> [...]
Here is the summary with links:
- Bluetooth: hci_core: Fix inquiry cache timestamps on 64-bit systems
https://git.kernel.org/bluetooth/bluetooth-next/c/ea983244b99a
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-22 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 2:01 [PATCH] Bluetooth: hci_core: Fix inquiry cache timestamps on 64-bit systems Linmao Li
2026-09-22 2:31 ` bluez.test.bot
2026-09-22 15:00 ` 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=179008921025.4126096.7212004044919126524.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=lilinmao@kylinos.cn \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=stable@vger.kernel.org \
/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.