From: Shermin Joy <shermin.joy@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [RFC v2 0/3] Use address resolution in controller to enable device filtering when peer uses RPA
Date: Mon, 9 Oct 2017 15:20:59 +0530 [thread overview]
Message-ID: <59db4626.c604630a.d36d6.d7ee@mx.google.com> (raw)
Changes since v1:
Resolving List is now maintained in LRU fashion. Devices are added
to the tail and removed from the head. When a connection or pairing
is made to a device, and its IRK is known, then it is pushed to the
end of the list, resulting in the LRU entry to be always at the head.
Shermin Joy (3):
Add HCI commands to enable address resolution in controller
Add and delete devices in the resolving list
Use whitelist along with resolving list to enable device filtering
include/net/bluetooth/hci.h | 25 ++++
include/net/bluetooth/hci_core.h | 15 +++
net/bluetooth/hci_core.c | 20 +++
net/bluetooth/hci_event.c | 103 ++++++++++++++++
net/bluetooth/hci_request.c | 258 ++++++++++++++++++++++++++++++++++++++-
net/bluetooth/hci_request.h | 12 ++
net/bluetooth/mgmt.c | 10 ++
net/bluetooth/smp.c | 4 +
8 files changed, 441 insertions(+), 6 deletions(-)
--
1.9.1
reply other threads:[~2017-10-09 9:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=59db4626.c604630a.d36d6.d7ee@mx.google.com \
--to=shermin.joy@gmail.com \
--cc=linux-bluetooth@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 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).