From: Roland McGrath <roland@redhat.com>
To: frysk@sources.redhat.com
Subject: avoid fc5 kernels > kernel-2.6.17-1.2187_FC5 and < 1.2243
Date: Fri, 17 Nov 2006 07:51:00 -0000 [thread overview]
Message-ID: <20061117075147.5339D180059@magilla.sf.frob.com> (raw)
I just discovered today that recent fc5 kernel updates are basically the
fc6 kernel rebuilt, including the utrace patch (and no doubt some
intermediate buggy version to boot). I've been recommending "the FC5
kernel" as the stable reference kernel using the old pre-utrace ptrace.
Recent updates are no good for that purpose and should be avoided.
kernel-2.6.17-1.2187_FC5 is the last fc5 updates rpm before the updates
started including buggy utrace code. For known-stable ptrace, please use
that for now or an earlier kernel that worked for you (my workstation has
been up for 41 days and it's running 2.6.17-1.2174_FC5).
I've asked the Fedora kernel maintainer to drop the utrace patch from fc5
update kernels, and the next update to go out will go back to the vanilla
upstream ptrace (may be a few days). The safe update will have a version
higher than 2.6.18-1.2243.
Thanks,
Roland
next reply other threads:[~2006-11-17 7:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 7:51 Roland McGrath [this message]
2006-11-21 17:24 ` Mark Wielaard
2006-11-21 20:22 ` Stan Cox
2006-11-22 11:59 ` Mark Wielaard
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=20061117075147.5339D180059@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=frysk@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).