linux-kernel - Re: [Demo/lkm] Kcoredump -- Do coredump in any where of kernel(not same with kcore)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 22 Sep 2009 22:18:19 +0800
From:	Hui Zhu <teawater@...il.com>
To:	Américo Wang <xiyou.wangcong@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [Demo/lkm] Kcoredump -- Do coredump in any where of kernel(not 
	same with kcore)

On Tue, Sep 22, 2009 at 17:31, Américo Wang <xiyou.wangcong@...il.com> wrote:
> On Tue, Sep 22, 2009 at 4:41 PM, Hui Zhu <teawater@...il.com> wrote:
>> Hi guys,
>>
>> Kcoredump do a coredump in most part of kernel (it use kprobe, it can
>> be set most of part of kernel).  For example:
>> insmod kcoredump.ko name=do_fork offset=11
>> gdb ./vmlinux /proc/kcoredump
>> Core was generated by `'.
>
> But what is your point of generating coredump anywhere?
> I mean what do you really want by this?

We can get the kernel status in do_fork+11 and put it to core file (It
like gdb command "gcore").  GDB can parse it.

>
> I think we can do this by systemtap+kdump, can't we?
>
It seems that kdump just can get core when kernel crash.

Thanks,
Hui
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/