Return-path: Received: from shards.monkeyblade.net ([149.20.54.216]:37369 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755666Ab3KLVNw (ORCPT ); Tue, 12 Nov 2013 16:13:52 -0500 Date: Tue, 12 Nov 2013 16:13:50 -0500 (EST) Message-Id: <20131112.161350.946584501122269943.davem@davemloft.net> (sfid-20131112_221401_477581_7DFEF511) To: davej@redhat.com Cc: netdev@vger.kernel.org, linux-bluetooth@vger.kernel.org, linux-wireless@vger.kernel.org Subject: Re: shutdown(3) and bluetooth. From: David Miller In-Reply-To: <20131112211125.GA2912@redhat.com> References: <20131112211125.GA2912@redhat.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Sender: linux-wireless-owner@vger.kernel.org List-ID: From: Dave Jones Date: Tue, 12 Nov 2013 16:11:25 -0500 > Is shutdown() allowed to block indefinitely ? The man page doesn't say either way, > and I've noticed that my fuzz tester occasionally hangs for days spinning in bt_sock_wait_state() > > Is there something I should be doing to guarantee that this operation > will either time out, or return instantly ? > > In this specific case, I doubt anything is on the "sender" end of the socket, so > it's going to be waiting forever for a state change that won't arrive. Adding bluetooth and wireless lists. Dave, please consult MAINTAINERS when asking questions like this, thanks!