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;
Content-Type: text/plain;
        charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Subject: Re: [PATCH] Bluetooth: Update resolving list when updating whitelist
From:   Marcel Holtmann <marcel@holtmann.org>
In-Reply-To: <CANFp7mXR+N7syYE6EdNH-+jE9r-uPHHfN8EvAFSUFUT7sbGVCw@mail.gmail.com>
Date:   Wed, 8 Apr 2020 08:15:24 +0200
Cc:     Bluez mailing list <linux-bluetooth@vger.kernel.org>
Content-Transfer-Encoding: 8BIT
Message-Id: <B424D264-32AB-47CE-BE13-6073887AE23E@holtmann.org>
References: <20200407205611.1002903-1-marcel@holtmann.org>
 <CANFp7mXR+N7syYE6EdNH-+jE9r-uPHHfN8EvAFSUFUT7sbGVCw@mail.gmail.com>
To:     Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

Hi Abhishek,

> Since the resolv list is tied directly to the whitelist, do we still
> need hdev->le_resolv_list? Maybe we should remove it.

it is really useful for debugging since you can look into debugfs to see what is actually programmed into the controller. I also have the feeling that eventually we might need the resolving list when we have privacy enabled.

Regards

Marcel