From: James Bourne <jbourne@hardrock.org>
To: Chris Frey <cdfrey@netdirect.ca>
Cc: Mark Symonds <mark@symonds.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.23 hard lock, 100% reproducible.
Date: Sun, 7 Dec 2003 11:49:42 -0700 (MST) [thread overview]
Message-ID: <Pine.LNX.4.51.0312071147070.3356@cafe.hardrock.org> (raw)
In-Reply-To: <20031207133201.A4744@netdirect.ca>
On Sun, 7 Dec 2003, Chris Frey wrote:
> On Sat, Dec 06, 2003 at 08:34:32PM -0800, Mark Symonds wrote:
> > Other than that, nothing. Is there a patch out there
> > that will simply make 2.4.22 secure? Things run great
> > on that kernel.
>
> Here's the relevant section from patch-2.4.23
Hi,
This is included with the patch set I just posted, 2.4.22-uv3 available at
http://www.hardrock.org/current-updates/linux-2.4.22-uv3-updates.patch.
This also includes patches for some other issues in 2.4.22. I haven't yet
posted one for 2.4.23 due to some outstanding issues with what appear to be
(or at least could be) hard locks (such as this thread). Once these are
resolved I will be releasing a -uv for 2.4.23.
Regards
James
>
> - Chris
--
James Bourne | Email: jbourne@hardrock.org
Unix Systems Administrator | WWW: http://www.hardrock.org
Custom Unix Programming | Linux: The choice of a GNU generation
----------------------------------------------------------------------
"All you need's an occasional kick in the philosophy." Frank Herbert
next prev parent reply other threads:[~2003-12-07 18:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-07 2:36 2.4.23 hard lock, 100% reproducible Mark Symonds
2003-12-07 3:30 ` Philippe Troin
2003-12-07 4:34 ` Mark Symonds
2003-12-07 18:32 ` Chris Frey
2003-12-07 18:49 ` James Bourne [this message]
2003-12-07 19:21 ` David Rees
2003-12-07 20:19 ` James Bourne
2003-12-07 6:50 Alex Davis
2003-12-07 6:55 ` William Lee Irwin III
[not found] ` <046a01c3bca1$267ba5e0$7a01a8c0@gandalf>
2003-12-07 9:07 ` William Lee Irwin III
2003-12-07 9:16 ` Keith Owens
2003-12-07 9:36 ` William Lee Irwin III
2003-12-08 16:34 ` Oliver Teuber
2003-12-07 10:01 ` Mark Symonds
2003-12-07 11:34 ` Martin Josefsson
2003-12-07 14:40 ` Marcelo Tosatti
2003-12-07 23:18 ` Mark Symonds
2003-12-08 4:53 ` William Lee Irwin III
2003-12-08 7:12 ` Tim Timmerman
2003-12-08 11:06 ` Marcelo Tosatti
2003-12-09 6:29 ` Tim Timmerman
2003-12-08 10:17 ` Marcelo Tosatti
2003-12-08 15:54 ` Stephan von Krawczynski
2003-12-08 16:15 ` Marcelo Tosatti
2003-12-08 16:31 ` Jeff Garzik
2003-12-08 16:55 ` Stephan von Krawczynski
2003-12-08 19:56 ` Mark Symonds
2003-12-07 7:33 ` Mark Symonds
2003-12-07 16:24 ` Alex Davis
2003-12-08 17:06 Xose Vazquez Perez
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=Pine.LNX.4.51.0312071147070.3356@cafe.hardrock.org \
--to=jbourne@hardrock.org \
--cc=cdfrey@netdirect.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@symonds.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).