From: Horms <horms@debian.org>
To: Nikos Ntarmos <ntarmos@ceid.upatras.gr>
Cc: 329354@bugs.debian.org,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Frederik Schueler <fs@lowpingbastards.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: CAN-2005-0204 and 2.4
Date: Mon, 26 Sep 2005 11:04:52 +0900 [thread overview]
Message-ID: <20050926020450.GA18357@verge.net.au> (raw)
In-Reply-To: <20050922135624.GA4346@diogenis.ceid.upatras.gr>
On Thu, Sep 22, 2005 at 04:56:24PM +0300, Nikos Ntarmos wrote:
> Hi there.
>
> On Thu, Sep 22, 2005 at 11:30:25AM +0900, Horms wrote:
> > The problem that you see is a patch that was included in 2.4.27-11
> > (the current version in sid), though it isn't built for amd64.
> >
> > Could you see if the following patch works for you.
>
> Yes it does. That's exactly what I also did to make it build, but I
> didn't send in a patch as I wasn't sure that 4 (sizeof(u32)) is the
> right factor for a 64-bit arch.
>
> > I've CCed lkml and Marcelo for their consideration. It seems to me
> > that 2.4 is indeed vulnerable to CAN-2005-0204, perhaps someone can
> > shed some light on this.
>
> My intuition agrees with yours. However, as also stated in #329355 by
> fs, "the amd64 port does not support 2.4 kernels, and there are no plans
> to change this", so I guess this is not-a-bug for debian/x86_64.
Well, its not a Debian bug as such, but it was an upstream
bug which has now been fixed and should appear in 2.4.32.
So your efforts weren't entirely in vain.
--
Horms
next prev parent reply other threads:[~2005-09-26 4:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1EI1tH-0006Yy-00@master.debian.org>
2005-09-22 2:30 ` CAN-2005-0204 and 2.4 Horms
2005-09-22 13:56 ` Nikos Ntarmos
2005-09-26 2:04 ` Horms [this message]
2005-09-22 20:04 ` Marcelo Tosatti
2005-09-23 22:17 ` [patch] x86_64: fix tss limit (was Re: CAN-2005-0204 and 2.4) Siddha, Suresh B
2005-09-23 22:55 ` Jesper Juhl
2005-09-23 23:22 ` Siddha, Suresh B
2005-09-23 23:25 ` Jesper Juhl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050926020450.GA18357@verge.net.au \
--to=horms@debian.org \
--cc=329354@bugs.debian.org \
--cc=fs@lowpingbastards.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=ntarmos@ceid.upatras.gr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.