Re: [linux-pm] Is it supposed to be ok to call del_gendisk whileuserspace is frozen?

From: Nigel Cunningham
Date: Sun May 16 2010 - 17:33:54 EST


On 17/05/10 05:38, Rafael J. Wysocki wrote:
On Sunday 16 May 2010, Nigel Cunningham wrote:

On 16/05/10 06:30, Rafael J. Wysocki wrote:
On Saturday 15 May 2010, Alan Stern wrote:
On Thu, 13 May 2010, Matt Reimer wrote:

I don't see anything wrong with the patch itself, but I dislike the
description. Devices can come and go from any hotpluggable bus, not
just MMC/SD. That just happens to be the first place the problem was

Good point. How about this?


From 813bd223e5a2fa577b9e64ddf12654a93d0aab8b Mon Sep 17 00:00:00 2001
From: Matt Reimer<mreimer@xxxxxxxxxxxxxx>
Date: Thu, 13 May 2010 14:36:54 -0700
Subject: [PATCH] fs: prevent hang on suspend/resume when MMC/SD card present

Devices can come and go bus during suspend or resume, when the
writeback thread is frozen, resulting in a hang. Prevent the hang
by thawing the writeback thread in del_gendisk().

I would have said "the block layer's writeback thread", but this is

OK, so now I have a question who's going to take the patch.

I object to the patch.

Tell the patch it ought to exit once thawed, by all means.

I'm not sure what you mean. Care to explain?

I mean "Set up some sort of flag that it can look at once thawed at resume time, and use that to tell it to exit at that point."

Make the patch unfreezeable to begin with, by all means.

That wouldn't work.

Why not?

But don't go down the path of having $random_code_path unfreeze a
thread. That will lead to unpredictability, confusion and bugs.

As a general rule, I agree, but this particular case is somewhat special.

If you know a disk is going to be unregistered during resume,

How do we check that, exactly?

Well, if you can figure out that you need to go down this path at this point in the process, you must be able to apply the same logic to come to the same conclusion earlier in the process.

use the hooks early in the suspend / hibernate process to block new I/O and
flush what's already there so that there's no need to block on the
writeback thread, and/or no need to have the writeback thread frozen.

I'm not sure if that's realistic. Do you have a specific implementation in

No - just the conviction that there must be a way in which the logic that says we need to call del_gendisk can be applied earlier to clean things up at an earlier stage.

I'd love to look at it further, but I'm moving house on Wednesday, so have a little bit of a pressing need to do some packing at the moment :) That said, next week, life is going to be very different - I could look at it then.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at