On Wed, Oct 12, 2011 at 12:44:29PM +0200, Borislav Petkov wrote: [..] > > > But, regardless, according to Vivek, the "makedumpfile" tool should be > > > able to jump over poisoned pages and you don't need all the hoopla above > > > at all, right? > > > > > > > In short, the answer is yes. We could add a new string, say > > "CRASH_REASON=PANIC_MCE" to VMCOREINFO elf-note which can be parsed by > > 'makedumpfile' and get away without adding the new NT_NOCOREDUMP > > elf-note. Parsing through the log_buf to lookout for panic string from > > inside 'makedumpfile' appears to be a clumsy solution though. > > Why, 'makedumpfile' reportedly supports some dmesg parsing already - > why would you need additional functionality when it can be done with > in-house means already. Maybe Vivek should comment on whether this makes > sense but I'm basically reiterating what he said. makdumpfile can extarct kernel log buf but it does not parse it. So it just extracts the logs and one can save it to a file and parsing it is left to user. So exporting one more string through VMCOREINFO to signal that PANIC_MCE happened makes sense to me. Rest of it can go into makedumpfile. Thanks Vivek
