This fixes a potential security issue on i386. FXRSTOR raises an #GP
when the MXCSR field in the FXSAVE frame contains illegal values. By
putting an signal frame just at a border to an unmapped page a malicious
user could potentially cause an exception in the context switch using this.
When the EFAULT occurs in the last bytes of the signal frame the MXCSR
check would be skipped in the old code, but the rogue value would be already
in task_struct, causing problems later.

Here is the minimal fix for this.

Originally discovered by Andrea while doing x86-64 work. It was fixed in
a different way a bit more intrusive way on x86-64 - all FXRSTOR in the
kernel are guarded by exception handlers.

It's nearly impossible to get the correct CPU names for AMD CPUs in
the MP table (would need BIOS calls etc.). The decoding of CPU names form
the mptable doesn't look too useful anyways, because the correct CPU name
from CPUID is printed only a few lines later. This patch just removes
the name table and replaces it with a printout of the hex value.
This mirrors a change in x86-64

Remove myself as networking maintainer. I haven't done much for networking
for a long time and it doesn't look likely it'll change anytime soon.
Also David/Alexey are doing a fine job without me.

Here is the big 2.5.21 x86-64 sync patch. It only touches arch/x86_64
and include/asm-x86_64. It requires a few other changes that I'm sending
in separate mail.

Changes:
- merge wit 2.5.21
- merge from 2.5.21/i386 (new PCI code, new LDT code etc.)
- sync with 2.4-x86_64 tree.
- minor updates to 32bit emulation
- better early console; including serial support.
- now set up dummy PDA for booting to avoid problems
- Fix GS reloading in context switch one instruction race
- Remove hardcoded names from mpparse code
- Fix inline assembly for RAID-5 xor (similar change needed for i386)
- Real per cpu data support based on PDA field
- Cleanup of offset.c generation requested by Kai: it only puts structure
  offsets into offset.h now.
- Fix i387 fxsave signal frame problems.
- Add uname emulation via personality ("linux32")
- New SSE optimized checksum-copy, copy*user, memcpy, clear_page, copy_page
  functions. Other tunings/cleanups in checksum and other user memory
  access function.
- check if exception table is really sorted
- Cleanups in page table handling in preparation of non executable pages
  support.
- Cleanup PDA access to not require offset.h (thanks to kai for kicking me
  to this)
- use long long for u64/s64 to avoid more warnings
- remove CONFIG_ISA
- fix various bugs and other cleanups

into home.transmeta.com:/home/torvalds/v2.5/linux

  enable/disable preemption to not spend too much time with
  preemption disabled. wait_task_inactive() can take quite some
  time occasionally ...

  set p->thread_info->cpu directly if the task is not running
  and is not on any runqueue.

into home.transmeta.com:/home/torvalds/v2.5/linux

into home.transmeta.com:/home/torvalds/v2.5/linux

Recent header cleanup broke this driver. Needs #include <linux/init.h>

ACPI interpreter update
Change non-interpreter code to account for the interpreter changes.

This update gets things compiling again after a device model change.

This adds preliminary support for _TRA resource on PCI root bridges (Bjorn
Helgaas)

into home.transmeta.com:/home/torvalds/v2.5/linux

end_request(int) turned to end_request(req, int); all old callers
are converted to end_request(CURRENT, value).  Now we can start
killing CURRENT/QUEUE - end_request() was the last obstacle to
that.

ditto for DEVICE_INTR/CLEAR_INTR.  do_mfm/do_acsi/do_hd/... are
explicitly declared in the drivers that use DEVICE_INTR stuff;
DEVICE_INTR/CLEAR_INTR is gone from blk.h.

#define DEVICE_NAME ... removed from the drivers that never use
that macro.

monstrous cascade of #ifdefs is gone from blk.h.  This is the first
step of cleanup - we move #define in question into the code that
includes blk.h (i.e. DEVICE_NR, DEVICE_NAME and DEVICE_INTR are
explicitly set by drivers).

->s_dev is switched to dev_t.  Everything that uses it uses it as
a number - i.e. all instances are either minor() or kdev_t_to_nr().

->j_dev is gone from reiserfs journal.  All its uses had been replaced
with use of ->j_dev_bd; it's simply not used anymore.

get_super() split in two functions - get_super(bdev) and
user_get_super(dev_t).  Callers that used get_super() to get superblock
by (dev_t) syscall argument switched to the latter; the rest had
block_device in question and switched to passing it.

ROOT_DEV converted to dev_t.  There's no reason for it to be kdev_t -
it's both used as a number and set as a number.

do_getattr() renamed to vfs_getattr(), exported and used by
loop.c and nfsd - both blindly accessed ->i_dev/->i_ino of
random inodes when they ought to be calling ->getattr() to
get that information.

misc gratitious kdev_t uses fixed (janitorial stuff - e.g. quota
patches had reintroduced kdevname(sb->s_dev) in places where we'd
switched to sb->s_id, etc.)

added bdev_read_only() - analog of is_read_only() using block_device.
Almost all callers of is_read_only() converted.

sget()/generic_shutdown_super() cleaned up; fixed error handling
in sget()

FS_NOMOUNT is gone, initialization for pseudo-filesystems
(bdev, pipe, sock) switched to use of a common helper.

compile fixes (missing includes + obvious fix in adfs/map.c)

pay attention to the return value of usb_control_msg as found by the CHECKER tool.

pay attention to return value of usb_submit_urb as found by the CHECKER tool.

This is a collected patch for USB drivers to use the new list macros
(list_del_init, list_move*).

 - Sync with 2.5.21

 - Don't call put_device inside idedisk_cleanup(). This is apparently triggering
   some bug inside the handling of device trees. Or we don't register the device
   properly within the tree. Check this later.

 - Further work on the channel register file access locking.  Push the locking
   out from __ide_end_request to ide_end_request.  Rename those functions to
   respective __ata_end_request() and ata_end_request().

 - Move ide_wait_status to device.c rename it to ata_status_poll().

 - Further work on locking scope issues.

 - devfs showed us once again that it changed the policy from agnostic numbers
   to unpleasant string names.