From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: kernel update (relative to 2.4.29)
Date: Mon, 14 Mar 2005 23:43:19 +0000 [thread overview]
Message-ID: <1110843799.4088.38.camel@eeyore> (raw)
The ia64 kernel patch for Linux 2.4.29 is available here:
ftp://ftp.kernel.org/pub/linux/kernel/ports/ia64/v2.4/linux-2.4.29-ia64-050312.diff.gz
The current 2.4-based ia64 tree is also available as a BitKeeper
repository. You can browse the changelog and the source files with a
normal browser at:
http://lia64.bkbits.net:8080/linux-ia64-2.4
or you can use the BitKeeper tools to maintain a local copy of the
tree like this:
$ bk clone bk://lia64.bkbits.net/linux-ia64-2.4 linux-ia64-2.4
Bjorn
IA64-related changes since 2.4.26:
* Perfmon:
- use seq_file for /proc to avoid buffer overflows (Stephane Eranian, Dean Nelson).
- fix /proc/pal/CPU*/bus_info descriptions (Stephane Eranian).
- fix perfmon "BEER promotion" typo (Stephane Eranian).
- clear sampling buffer at init (Stephane Eranian).
* Misc bug-fixes:
- allow IO port space without EFI RT attribute (Bjorn Helgaas).
- fix FPH state check to keep task from seeing another task's regs (Arun Sharma).
- fix pte_modify bug that allowed mprotect() to change too many bits (David Mosberger).
- add unw_unwind_to_user() sanity check (Keith Owens).
- add missing syscall slot.
- fix ptrace corner cases (Yanmin Zhang).
N.B. While testing this patch, I noticed that the ptrace fixes caused
anything linked with the profiling libc in Debian to fail. The same
thing happens with the current 2.6 kernel, so I think the problem is
most likely in the Debian profiling libc.
next reply other threads:[~2005-03-14 23:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 23:43 Bjorn Helgaas [this message]
2005-03-15 0:42 ` kernel update (relative to 2.4.29) Keith Owens
2005-03-21 22:06 ` David Mosberger
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=1110843799.4088.38.camel@eeyore \
--to=bjorn.helgaas@hp.com \
--cc=linux-ia64@vger.kernel.org \
/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.