Fix a couple of ext3 error handling routines to not assume that the
superblock has valid journal and buffer_head pointers.  These functions are
called during mount and unmount and that may not be true.

This should fix the oops which Zwane saw when mounting a corrupt filesystem.

I enabled the advanced use-after-free detector for large slab objects and the
kernel oopsed.  This is because that debug code adds things at the head of
the slab objects, and the kernel will die if task_structs are not
well-aligned.

The way to tell the slab allocator that it is not allowed to misalign objects
from this slab is SLAB_MUST_HWCACHE_ALIGN.

Patch from Oleg Drokin <green@linuxhacker.ru>

There seems to be a memleak on error exit path.

Patch from Oleg Drokin <green@linuxhacker.ru>

   Not freeing allocated memory on error exit path.

Patch from Petr Vandrovec <vandrove@vc.cvut.cz>
Reported by Oleg Drokin.

    In NCP_IOC_SETOBJECTNAME handler, we allocated space (newname pointer),
    copy stuff from userspace to there and then assign userspace
    pointer to our internal structure, whoops!

Force inlining even when gcc-3.x is too confused to do it for us.

The conversion of the console registration to an initcall-style thing has
broken lots of people's setups.  It is now dependent upon linkage order and
if you have both CONFIG_VT_CONSOLE and CONFIG_SERIAL_CONSOLE, no boot
messages come out on the screen because the kernel is selecting the serial
console first.

It can be fixed by specifying console=tty0, but nobody is doing that.

We can fix it up by placing drivers/char/ in front of drivers/serial/ in
linkage order.

The pnp_request_card_device() stub should return NULL, not -ENODEV.

Patch from Andreas Mohr <andi@rhlx01.fht-esslingen.de>

Need to retake the spinlock in __pdflush() before continuing.

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

Make x86-64 boot again after the INITIAL_JIFFIES changes
and some bug fixes. Also some work for NPTL.

 - Merge with i386/2.5.64-bk3
 - Fix memory leak in copy_thread
 - arch_prctl uses GDT for base if possible. Cleanup.
 - clone supports bases >32bit for SETTLS etc. %fs hardcoded now.
 - new ptrace support for 64bit TLS
 - Disable (set|get)_thread_* for 64bit processes.
 - Audit arch/x86_64 for jiffies wrap issues.
 - Fix initial jiffies problem (that caused hanging kernels)
 - FIx a few 32bit emulation bugs (sigaltstack, sigqueue)
 - Some cleanup from Pavel
 - Should compile again as UP
 - Shrink size a bit by not putting exception tables into object files.
 - Fix compilation with gcc 3.3 :- force inlining when needed
 - Work around 2.5.64-bk3 console init bug.
 - Fix some alignments in assembly code

Rationale:  devfs_only does nothing but disabling {un,}register_blkdev
and {un,}register_chrdev.  {un,}register_blkdev already do nothing but
adding it's name argument to a lookup table for the __bdevname and
/proc/device output so this use is already bogus.  The disabling of
the character device per-major arrays can work in practice but is
useless as any driver relying on it can't be used on non-devfs systems.

Cleanup the i2c procfs code a bit (less ifdef mess), partially based
on the lm_sensors CVS code.

This fixes a bunch of "src" versus "obj" confusions that apparently
existed in my bootsect removal patch.  How embarrassing...

This recent patch caused Nick Piggin's 2xPIII VIA686B chipset machine into an
interrupts-off lockup during IDE probing.

We don't really know why - it might be because an interrupt is delivered to a
secondary which doesn't expect it.

I have a second patch from Zwane which solves the same problem in a different
way, but until that's had some wider testing I suggest we just back off the
original.

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

 - Fix my email address to one which reaches me ;-)
 - Remove timer.h include as we don't use timers.
 - Add module.h.
 - Sort includes alphabetically.
 - Move EXPORT_SYMBOL from ksyms.c to locks.c.
 - Simplify locks_conflict().

entry routine load the real ESP0 off that per-cpu stack. Make this
even faster by putting the sysenter stack in the per-CPU TSS, so
that we can use the tss->esp0 value directly (which we have to
update on task switches anyway).

CAREFUL! This needs very subtle code for debug and NMI exceptions,
to make sure we don't run with the sysenter stack in any real kernel
code!

use the real ones instead.

into nuts.ninka.net:/home/davem/src/BK/net-2.5

This patch is a update for the video-buf mm helper module.  It has
some minor bugfixes and a number of signed/unsigned cleanups to make
gcc 3.3 happy.

This allows us to avoid having to use atomic updates for the lazy FP
status setting, since we don't have to worry about other CPU's racing
on the fields.

Also, fix x86 FP state after fork() by making sure the FP is unlazied
_before_ we copy the state information. Otherwise, if a process did a
fork() while holding the FP state lazily in the registers, the child
would incorrectly unlazy bogus state.

Fixes many issues that were discovered after testing.  Also cleans up the
card service code and fixes the card_drvdata bug in which only one driver
at a time could have driver data.

Compatibility update for the latest changes.

Updates the als100 driver to use the pnp apis.  Includes resource config
templates.

This set of changes addresses the following issues with the existing card 
service implementation:

1.) Only one driver can be bound to a card.
2.) repetive code is required for pnp_request_card_device and other 
functions

This patch will make the card services usable by ALSA.

into neo.rr.com:/home/ambx1/src/bk/linus-2.5

A few minor revisions.  Simpifies a few commands and adds config mode 
information.

the otherwise unused cpl1 entry for SS), so that we can avoid
re-loading it on task switches if it doesn't change.

If we raced on a timer expire, we'd get a negative timeout and think
that is was a _huge_ positive timeout. 

to speed it up - use the proper bitmask for clearing "used-fpu"
state.

Following some changes on x86-64.

When cpu_has_fxsr is defined to 1 like in many kernels unlazy_fpu can
collapse to three instructions. For that inlining is a very good idea.
Otherwise it's 10 instructions or so, which can be still inlined.

We don't need the lock prefix to test our local thread flags state.
Unfortunately test_thread_flag currently always uses test_bit which
has a LOCK on SMP, but that's unnecessary. LOCK is costly on P4,
so it's a good idea to avoid it.

Work around this for now by testing directly. Better would be
probably to define __set_bit for all architectures to not guarantee
atomicity and then always use that for local thread_info accesses
in linux/thread_info.h

Without this we have a choice between dropping lots of counter events
for counters > 0, or getting dazed and confused.  This brings it inline
with the 2.4 module code.  Tested on my 2-way.

Also fix a typo from Steven Cole, and remove some unnecessary code

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

into raven.il.steeleye.com:/home/jejb/BK/scsi-for-linus-2.5

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