This patch just disables core file from some of the executables.
Not sure how it can affect your initrd... Only if it crashes somewhere,
which should not normally happen.
Can you please recheck, that this is exactly this patch?

Plus, I don't understand how you managed to apply this patch to 028stab039.
This patch is already included in OpenVZ kernels since long ago 028test015...
So maybe it was applied by you 2nd time somehow and with wrong context?

Thanks,
Kirill


Dariush Pietrzak wrote:
> The patch is: core-dumping unreadable binaries via PT_INTERP
> it's described as:
> 
> "
> From: Alexey Dobriyan <adobriyan@openvz.org>
> Date: Fri, 26 Jan 2007 08:57:16 +0000 (-0800)
> Subject: [PATCH] core-dumping unreadable binaries via PT_INTERP
> X-Git-Tag: v2.6.20-rc7^0~60
> X-Git-Url:
> http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Ftorvalds%2Flinux-2.6.git;a=commitdiff_plain;h=1fb844961818ce94e782acf6a96b92dc2303553b
> 
> [PATCH] core-dumping unreadable binaries via PT_INTERP
> 
> Proposed patch to fix #5 in
> http://www.isec.pl/vulnerabilities/isec-0017-binfmt_elf.txt
> 
> ....
> Check for MAY_READ like binfmt_misc.c does.
> 
> Signed-off-by: Alexey Dobriyan <adobriyan@openvz.org>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
> "
> 
> and when applied to 2.6.18 ovz028stab039.1, it stops my kernels
> from booting ( they fail to find root filesystem in initrd and
> hang there waiting for it to appear ).
>  Where do I report it ( or maybe how can I check if this has been
> fixed in the meantime? )
>