Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Reply-To: jay@systech.com
To:     linux-bluetooth@vger.kernel.org
From:   Jay Foster <jay@systech.com>
Subject: Bluez Socket File Descriptor Leak
Organization: Systech Corporation
Message-ID: <749228e2-4d49-83ef-06f0-2db0532beb93@systech.com>
Date:   Fri, 4 Jun 2021 12:06:48 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.11.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Precedence: bulk

I am experiencing an odd problem with PAN networking.  I have PAN 
networking setup in NAP role.  Another machine makes a BNEP connection 
and performs network activity, then disconnects the BNEP connection.  
This repeats periodically.  This works just fine, except after a while, 
the BNEP connection fails with the following in the log.

May  4 13:08:02 (none) daemon.debug bluetoothd[1373]: 
profiles/network/server.c:confirm_event() BNEP: incoming connect from 
B8:27:EB:E5:35:9B
May  4 13:08:03 (none) daemon.err bluetoothd[1373]: Can't add bnep0 to 
the bridge br1: Too many open files(24)

ls /proc/`pidof bluetoothd`/fd shows about 1000 open file descriptors 
(sockets mostly).  This looks like some kind of resource (file 
descriptor) leak.

Has anyone experienced this before?  I don't know if it is in the 
bluetoothd application or one if the libraries (glib2, dbus) it links 
with.  Happens with bluez 5.19 and 5.52.

Jay