Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Christian Kellner <ckellner@redhat.com>
To:     linux-bluetooth@vger.kernel.org
Cc:     Mario.Limonciello@dell.com
Subject: BT advertising packets and s2idle issue
Organization: Red Hat
Date:   Mon, 29 Jul 2019 16:33:28 +0200
Message-ID: <87sgqoewqv.fsf@kellner.me>
MIME-Version: 1.0
Content-Type: text/plain
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk


Hi all,

I have been wondering what to do about the bug that advertising packet
will wake systems from s2idle when a device was previously paired with
the HCI_AUTO_CONN_ALWAYS flag (kernel bug #200039[1]). I was thinking of
creating a patch for bluez that would create a "delay lock"[2] and
de-register any such device from the kernel before entering s2idle, but
I wanted to check first if that is the best approach.
In comment #27 it is suggested that using a "LE Privacy v1.2" feature
could fix the issue as well. Is there some more information about this
available somewhere?  II can help out with development and testing as I
have an affected system myself.

Cheers,
CK

[1] https://bugzilla.kernel.org/show_bug.cgi?id=200039
[2] https://www.freedesktop.org/wiki/Software/systemd/inhibit/

--
Dr. Christian J. Kellner
Desktop Hardware Enablement
Red Hat