Re: [PATCH v7 0/6] solve deadlock caused by memory allocation with I/O
From: Oliver Neukum
Date: Thu Jan 17 2013 - 04:44:10 EST
On Thursday 17 January 2013 09:28:14 Ming Lei wrote:
> - we still need some synchronization to avoid accessing the storage
> between sys_sync and device suspend, just like system sleep case,
> pm_restrict_gfp_mask is needed even sys_sync has been done
> inside enter_state().
>
> So looks the approach in the patch is simpler and more efficient,
Even worse. The memory may be needed to resume and the reason
we need to resume may be that we need to write out memory. And
there is no way to make sure we don't dirty memory unless user space
is frozen, so it is either this approach, or GFP_NOIO in the whole resume
code path.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/