On Mon, Jan 03, 2005 at 03:25:41PM -0800, Matt Zimmerman wrote:
> On Wed, Dec 15, 2004 at 11:27:58AM +0900, Horms wrote:
>
> > On Wed, Dec 15, 2004 at 12:59:24AM +0100, Tomasz Malesinski wrote:
> > > Why hasn't the bug #266882 (CAN-2004-0554 i387.h in kernel: asm
> > > volatile("fnclex ; fwait");)
Horms wrote:
> On Mon, Jan 03, 2005 at 03:25:41PM -0800, Matt Zimmerman wrote:
> > On Wed, Dec 15, 2004 at 11:27:58AM +0900, Horms wrote:
> >
> > > On Wed, Dec 15, 2004 at 12:59:24AM +0100, Tomasz Malesinski wrote:
> > > > Why hasn't the bug #266882 (CAN-2004-0554 i387.h in kernel: asm
> > > > vol
On Fri, Jan 07, 2005 at 11:41:51AM +0900, Horms wrote:
> Understood. Would it be helpful if security patches for the 2.4 kernel
> were forwarded to the security-team as they are added to SVN for
> inclusion in unstable and thus testing?
Yes, absolutely.
> Perhaps being better about opening entri
On Mon, Jan 03, 2005 at 03:25:41PM -0800, Matt Zimmerman wrote:
> On Wed, Dec 15, 2004 at 11:27:58AM +0900, Horms wrote:
>
> > On Wed, Dec 15, 2004 at 12:59:24AM +0100, Tomasz Malesinski wrote:
> > > Why hasn't the bug #266882 (CAN-2004-0554 i387.h in kernel: asm
> > > volatile("fnclex ; fwait");)
On Wed, Dec 15, 2004 at 11:27:58AM +0900, Horms wrote:
> On Wed, Dec 15, 2004 at 12:59:24AM +0100, Tomasz Malesinski wrote:
> > Why hasn't the bug #266882 (CAN-2004-0554 i387.h in kernel: asm
> > volatile("fnclex ; fwait");) has not been fixed in 2.4.18 for so long?
>
> That and a host of others.
On Wed, Dec 15, 2004 at 12:59:24AM +0100, Tomasz Malesinski wrote:
> Why hasn't the bug #266882 (CAN-2004-0554 i387.h in kernel: asm
> volatile("fnclex ; fwait");) has not been fixed in 2.4.18 for so long?
That and a host of others. Security-Team, Is there ever going to be a
new kernel for Woody?
Why hasn't the bug #266882 (CAN-2004-0554 i387.h in kernel: asm
volatile("fnclex ; fwait");) has not been fixed in 2.4.18 for so long?
Tomasz MalesiĆski
7 matches
Mail list logo