OpenVZ Forum


Home » Mailing lists » Users » Re: [Fwd: Problem with patch by openvz, where should I report that?]
Re: [Fwd: Problem with patch by openvz, where should I report that?] [message #20469] Mon, 17 September 2007 06:14
Alexey Dobriyan is currently offline  Alexey Dobriyan
Messages: 195
Registered: August 2006
Senior Member
From: openvz.org
On Sat, Sep 15, 2007 at 01:46:17PM +0400, Kir Kolyshkin 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

How did you manage to do that? I mean, this patch is already in
patch-ovz028stab039.1-combined.

> 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? )
Previous Topic: Error after install a new kernel and reboot
Next Topic: vzctl start 777 -> RTNETLINK answers: No such device
Goto Forum:
  


Current Time: Mon Jul 15 22:33:33 GMT 2019