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] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 29 Oct 2009 16:52:05 +0900
From:	Jin Dongming <jin.dongming@...css.fujitsu.com>
To:	Vivek Goyal <vgoyal@...hat.com>
CC:	LKLM <linux-kernel@...r.kernel.org>,
	Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>,
	Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Lon Hohberger <lhh@...hat.com>,
	Neil Horman <nhorman@...hat.com>
Subject: Re: [PATCH] [RFC][Patch x86-tip] add notifier before kdump

Hi Vivek

Vivek Goyal wrote:
> - Other thing, I think Eric Biederman suggested was that we need to see
>   the code that will be executed after crash so that it can be audited and
>   keep it in kernel instead of blindly exporting a hook to module and let
>   module do whatever it want to do.
> 

I am sorry for that I could not catch the meaning of above words. In my
understanding:
    If the code is already in current kernel and no matter whether it is built
    or modulized, the code could be added before crash_kexec. Is it right?

If my understanding is not right, please let me ask a question before we
provide the code.
    What kind of code is considered as nice code and could be added into
    current kernel? Could you give me some requirements or examples
    about nice code?
    
Best regards,
Jin Dongming

> So my question is, how about introducing some infrastructure in kdump
> initrd to send a notification out?
> 
> Thanks
> Vivek

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ