On Sat, Nov 03, 2007 at 11:36:00AM +0100, Jan Niehusmann wrote: > > On Sat, Nov 03, 2007 at 10:43:41AM +0100, Jan Niehusmann wrote: > > On Fri, Nov 02, 2007 at 10:45:03PM +0000, Debian Bug Tracking System wrote: > > > This bug is fixed in the version mentioned above. > > > > > > > EIP: 0060:[<c0138a6d>] Not tainted VLI > > > > EFLAGS: 00210046 (2.6.22-2-vserver-686 #1) > > > > > > This is the wrong version. > > > > Oops, sorry, indeed I did update between reproducing the bug and > > sending the report. But I didn't find the mentioned patch in the source > > of -3, and no related changelog entry, so I assumed it was not fixed. > >
SNIP > The confusion is probably caused by the fact that upstream did modify > the patch after release, without changing the version number. At least > this is what I get from the upstream changelog: > > | ADDENDUM: The patch was re-released on 11 Oct 2007, which also included: > | > | * fix reference counting of vxi's in POSIX timer code > > Which, once again, proves that changing a release without changing the > version number is bad practice :-( > It seems that the linux-image-2.6.22-3-vserver-686 contains patch version 2.2.0.5 (see #482177), which should have included the fix for your problem. So I guess that Bastian was right in closing the bug. My 2 cents, Best regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
