From: Chris Down <chris@chrisdown.name>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@fb.com,
Jaganath Kanakkassery <jaganath.k.os@gmail.com>
Subject: Re: [PATCH] Bluetooth: hci_event: Mask data status from LE ext adv reports
Date: Fri, 18 Jul 2025 16:13:55 +0800 [thread overview]
Message-ID: <aHoCQ_RfBl5Zm4oQ@chrisdown.name> (raw)
In-Reply-To: <CABBYNZJo48983SWhxcB7UzWXPeUofRCMhQ8mJjih-rJoTET3_Q@mail.gmail.com>
Hi Luiz,
Thanks for the review!
Luiz Augusto von Dentz writes:
>Can you include a sample trace of the above?
Is that with btmon or similar? Sorry, I'm not a regular contributor to this
subsystem :-)
I mostly have a personal desire to get this merged because it's a particularly
noisy case where I happen to live :-) These are all with 0x40:
% dmesg | wc -l
3815
% dmesg | grep -c 'Unknown advertising'
3227
>Also it would be great to have a mgmt-tester for example that attempts to
>generate an advertisement like that to exercise such change.
Looks like that's in Bluez userspace code right, so what's the order of doing
these things?
>> - if (evt_type == LE_EXT_ADV_NON_CONN_IND ||
>> - evt_type & LE_EXT_ADV_DIRECT_IND)
>> + if (pdu_type == LE_EXT_ADV_NON_CONN_IND ||
>
>I'm not sure I would keep checking for LE_EXT_ADV_NON_CONN_IND, maybe
>just return LE_ADV_NONCONN_IND, LE_EXT_ADV_NON_CONN_IND is not
>actually a bit it is the absence of any bits being set, so I guess the
>only invalid adv are the ones for legacy which seem to require a bit
>to be set.
So are you thinking of doing this?
if (!(pdu_type & ~(LE_EXT_ADV_DIRECT_IND)))
return LE_ADV_NONCONN_IND;
Thanks for your help!
Chris
next prev parent reply other threads:[~2025-07-18 8:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 17:14 [PATCH] Bluetooth: hci_event: Mask data status from LE ext adv reports Chris Down
2025-07-17 19:12 ` Luiz Augusto von Dentz
2025-07-18 8:13 ` Chris Down [this message]
2025-07-18 16:05 ` Luiz Augusto von Dentz
2025-07-19 16:04 ` Chris Down
2025-07-21 13:34 ` Luiz Augusto von Dentz
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=aHoCQ_RfBl5Zm4oQ@chrisdown.name \
--to=chris@chrisdown.name \
--cc=jaganath.k.os@gmail.com \
--cc=kernel-team@fb.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).