From: Scott Branden <sbranden@broadcom.com>
To: "Andrew E. Mileski" <andrewm@isoar.ca>,
Brian Norris <computersforpeace@gmail.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: Hang on reboot in nand_get_device()
Date: Mon, 9 Nov 2015 12:49:41 -0800 [thread overview]
Message-ID: <564106E5.8020804@broadcom.com> (raw)
In-Reply-To: <5640FA8A.3010209@isoar.ca>
On 15-11-09 11:56 AM, Andrew E. Mileski wrote:
> 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.
Yes, the last operation can still be in flight - there are async cleanup
threads running in the UBI/UBIFS layers which recreated this problem.
>
> ~~Andrew E. Mileski
next prev parent reply other threads:[~2015-11-09 20:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 19:21 Hang on reboot in nand_get_device() Andrew E. Mileski
2015-11-06 18:00 ` Brian Norris
2015-11-06 18:59 ` Boris Brezillon
2015-11-09 19:46 ` Brian Norris
2015-11-09 19:56 ` Andrew E. Mileski
2015-11-09 20:49 ` Scott Branden [this message]
2015-11-09 20:55 ` Boris Brezillon
2015-11-09 21:36 ` Boris Brezillon
2015-11-09 21:44 ` Brian Norris
2015-11-09 21:51 ` Scott Branden
2015-11-10 0:22 ` Brian Norris
2015-11-09 18:43 ` Andrew E. Mileski
2015-11-09 19:16 ` Brian Norris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=564106E5.8020804@broadcom.com \
--to=sbranden@broadcom.com \
--cc=andrewm@isoar.ca \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.