From owner-freebsd-hackers@freebsd.org Sun Mar 10 10:26:53 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0DA88152EB56 for ; Sun, 10 Mar 2019 10:26:53 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 48FA86F4F1 for ; Sun, 10 Mar 2019 10:26:52 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id x2AAQTEh046271 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 10 Mar 2019 12:26:32 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua x2AAQTEh046271 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id x2AAQTsI046270; Sun, 10 Mar 2019 12:26:29 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 10 Mar 2019 12:26:29 +0200 From: Konstantin Belousov To: Hans Petter Selasky Cc: Warner Losh , FreeBSD Hackers , "O'Connor, Daniel" Subject: Re: USB stack getting confused Message-ID: <20190310102629.GQ2492@kib.kiev.ua> References: <3B29D870-41F9-46AF-B9F3-03106DEC417D@dons.net.au> <20190309152613.GM2492@kib.kiev.ua> <20190309162640.GN2492@kib.kiev.ua> <20190309192330.GO2492@kib.kiev.ua> <20190310094758.GP2492@kib.kiev.ua> <35f69493-4bbb-4142-b61a-3e90adc8777b@selasky.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <35f69493-4bbb-4142-b61a-3e90adc8777b@selasky.org> User-Agent: Mutt/1.11.3 (2019-02-01) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tom.home X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Mar 2019 10:26:53 -0000 On Sun, Mar 10, 2019 at 11:18:36AM +0100, Hans Petter Selasky wrote: > On 3/10/19 10:47 AM, Konstantin Belousov wrote: > >> Yes, I can do that if destroy_dev() ensures that d_close is called for > >> all open file handles once and only once before it returns. I think this > >> is where the problem comes from. > > See above. For d_close it is impossible, for cdevpriv dtr it is already > > there by design. > > > > Yes, cdevpriv_dtr will wait for the final close() from user-space > unfortunately. Or am I mistaken? You are mistaken. Cdevpriv destructors are called either on the file close (not the last close in d_close sense, just file close) OR during destroy_dev(). Each destructor/file pair is called exactly once, regardless of the cause.