Messages in this thread | | | Date | Fri, 30 Jul 2010 13:14:32 +0900 | From | KAMEZAWA Hiroyuki <> | Subject | Re: Memory corruption during hibernation since 2.6.31 |
| |
On Thu, 29 Jul 2010 21:10:10 -0700 Hugh Dickins <hughd@google.com> wrote:
> 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. > Okay ;) (And I forget that kexec has to prepare memory at boot time for 2nd kernel. It will be harmful for small device guys.)
I'll prepare a routine not-quick-fix. BTW, after reading mail between you and Andrea, kernel threads are not guaranteed to be stopped when memory-dump is running ?
-Kame
| |