From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 206-248-167-68.dsl.teksavvy.com ([206.248.167.68] helo=mail.isoar.ca) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1ZvsZ6-0003bZ-H9 for linux-mtd@lists.infradead.org; Mon, 09 Nov 2015 19:57:21 +0000 Message-ID: <5640FA8A.3010209@isoar.ca> Date: Mon, 09 Nov 2015 14:56:58 -0500 From: "Andrew E. Mileski" MIME-Version: 1.0 To: Brian Norris , Boris Brezillon CC: linux-mtd , Scott Branden Subject: Re: Hang on reboot in nand_get_device() References: <55958F4C.1020002@isoar.ca> <20151106180052.GE12143@google.com> <20151106195903.0d55d819@bbrezillon> <20151109194651.GI12143@google.com> In-Reply-To: <20151109194651.GI12143@google.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 2015-11-09 14:46, Brian Norris wrote: > > No, and that's the point of "getting" the device, without actually > releasing it. (Andrew's suggestion is essentially a > nand_release_device().) We don't want any other process picking up any > I/O at this point. I suppose there really is no way to begin any new > I/O, but it does seem possible for the last operation to still be in > flight, at least according to Scott's reports. That right there. is the very reason I questioned whether my approach was sufficient. ~~Andrew E. Mileski