Messages in this thread | | | Date | Thu, 29 Jul 2010 21:10:10 -0700 | Subject | Re: Memory corruption during hibernation since 2.6.31 | From | Hugh Dickins <> |
| |
On Thu, Jul 29, 2010 at 5:01 PM, KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> I think the best way is kexec(). But maybe rollback from hibernation failure > will be difficult. Considering how crash-dump works well and under maintainance > by many enterprise guys, hibernation-by-kexec is a choice. I think. It can make > reuse of kdump code, ...or, hibernation-resume code can eat kdump image > directly. Maybe the problem will be the speed of dump.
I've no appetite for a total rework of hibernation, and I don't see how that would address the issue: I'm just looking for some protection against swap reuse danger.
Hugh
| |