Hi Ivan, sorry for the delay. -----Original Message----- > These patchset suggests feature to add user specific information along > with dumpfile. One of usecases could be a platform build information > containing dubug file addresses, sources of daily build, some > platform related information and more, it's gracefully simplifies > debugging process, since an engineer doesn't need to spend time on > finding to which platform this core file is related, where to get > debugging counter part and so on. As user info can be added along with > dumpfile it frees platform from creating tar achieve spending doubled > space or using specific tools. Hmm, currently I don't think it will be worth making makedumpfile have the memo-like feature even with accepting some code and complexity. If makedumpfile can access that helpful data in 2nd kernel, kdump tool will be able to place it next to the dumpfile. There will become two files to be handled, but I'm not sure what the problem is with it.. Thanks, Kazu > Since this information is sorted and > selected by user it can't be standardized and should be placed in some > special generic section. This patchset roughly proposes the variant when > user information is placed/retrieved as subsection of note elf > section. > > Ivan Khoronzhuk (4): > makedumpfile: rename check_dump_file() on check_file_is_writable() > elf: add new "userinfo" ELF section to traverse debug information > elf_info: make int note_descsz() and offset_next_note() public > elf: add ability to read the userinfo data from note segment > > elf_info.c | 4 +- > elf_info.h | 5 + > makedumpfile.c | 393 ++++++++++++++++++++++++++++++++++++++++++++++++- > makedumpfile.h | 12 ++ > 4 files changed, 404 insertions(+), 10 deletions(-) > > -- > 2.20.1 _______________________________________________ kexec mailing list kexec@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/kexec
