diff options
| author | WANG Chao <[email protected]> | 2014-04-07 15:38:51 -0700 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2014-04-07 16:36:06 -0700 |
| commit | c4082f36fa3eeb5d4fadc50241b6e3a388561f80 (patch) | |
| tree | 1a33e8dcd80e5b73504fd27ad13b985687df438c /tools/perf/scripts/python | |
| parent | 82e0703b6ca8b549952c1e4f04746f27eaec012d (diff) | |
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 <[email protected]>
Cc: Vivek Goyal <[email protected]>
Cc: HATAYAMA Daisuke <[email protected]>
Cc: Greg Pearson <[email protected]>
Cc: Baoquan He <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions