summaryrefslogtreecommitdiffstats
path: root/lib
diff options
context:
space:
mode:
authorWANG Chao <chaowang@redhat.com>2014-04-07 15:38:51 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2014-04-07 16:36:06 -0700
commitc4082f36fa3eeb5d4fadc50241b6e3a388561f80 (patch)
tree1a33e8dcd80e5b73504fd27ad13b985687df438c /lib
parent82e0703b6ca8b549952c1e4f04746f27eaec012d (diff)
downloadlinux-c4082f36fa3eeb5d4fadc50241b6e3a388561f80.tar.bz2
vmcore: continue vmcore initialization if PT_NOTE is found empty
Currently when an empty PT_NOTE is detected, vmcore initialization fails. It sounds too harsh. Because PT_NOTE could be empty, for example, one offlined a cpu but never restarted kdump service, and after crash, PT_NOTE program header is there but no data contains. It's better to warn about the empty PT_NOTE and continue to initialise vmcore. And ultimately the multiple PT_NOTE are merged into a single one, all empty PT_NOTE are discarded naturally during the merge. So empty PT_NOTE is not visible to user space and vmcore is as good as expected. Signed-off-by: WANG Chao <chaowang@redhat.com> Cc: Vivek Goyal <vgoyal@redhat.com> Cc: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com> Cc: Greg Pearson <greg.pearson@hp.com> Cc: Baoquan He <bhe@redhat.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions