[Users] Problem with patch by openvz, where should I report that?

[Dariush Pietrzak]

On Mon, 17 Sep 2007, Kirill Korotaev wrote:

> 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?
 My bad, it got applied 2nd time, resulting in garbled, but compilable
code, but it applies rather cleanly to 028stab039, and patch does not
complain that the patch is reversed, which is rather unusual.
 I guess the fact that patch just adds lines and not modifies anything
helped.

 How should I go about applying bugfixes to 028stab039, I went through list
of bugfixes for 2.6.18 and applied them to ovz sources when one of my
machines got oops that is fixable by this:

X-Git-Url:
http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Ftorvalds%2Flinux-2.6.git;a=commitdiff_plain;h=9ad0830f307bcd8dc285cfae58998d43b21727f4
[PATCH] Keys: Fix key serial number collision handling

 since ovz contains some of the fixes, and omits some others, I had
to check this experimentally - I skipped those that are already applied
(which I test by check if reversed patch applies) and applied only those
that could be applied with little fuzz... the PT_INTERP patch
unfortunatelly went through the procedure as 'not already applied and
applying cleanly'.

 Maybe some list of fixes allready included in given ovz patch would help
in avoiding similar situation in the future, would it be possible to get
such list?

regards, eyck
-- 
Key fingerprint = 40D0 9FFB 9939 7320 8294  05E0 BCC7 02C4 75CC 50D9
 Total Existance Failure