In SCSI messages, sdsdd should have been sdd.
That is, these days error printing is a bit broken.

Fixes a "Bad page state at destroy_compound_page" error.

This fixes a sleep-in-spinlock bug for binfmt_misc registration.

That lock is purely for the list, not for the dentry.

Only set the rate/resolution if the user actually asked
for it. Some mice and KVM switches don't like to have
their rate forced.

exit_notify() used to leave a window open when a thread
died that made the thread visible as a ZOMBIE even though
the thread reaped itself. This closes that window by marking
the thread DEAD within the tasklist_lock.

into home.osdl.org:/home/torvalds/v2.5/linux

into home.osdl.org:/home/torvalds/v2.5/linux

Force Device-Mapper to use PAGE_SIZE or smaller I/O when the underlying
device has a bvec_merge_fn routine registered.  This will fix the
situation of Device-Mapper submitting I/Os to RAID-0 that span the
RAID-0 chunk boundaries.

Joe is working on a better solution that actually honors the MD
merge_bvec_fn routine.  But this minimal change will fix the problem for
the time being.

enable on UP-PREEMPT.

Without this, the enable could "migrate" up into the critical
region (on SMP, the actual spinlock would act as an additional
barrier and PREEMPT was ok).

I am still not sure that this change all by itself is enough
to make us accept zero initial timestamps properly. 

Cset exclude: davem@nuts.ninka.net|ChangeSet|20031025060257|60993

Cset exclude: kuznet@ms2.inr.ac.ru|ChangeSet|20031021052951|52463

We updated ip_nat_setup_info to set the initialized flag and call
place_in_hashes, but *didn't* change the call in ip_fw_compat_masq.c
which also calls place_in_hashes() itself (again!).  Result: corrupt
list, and next thing which lands in the same hash bucket goes boom.

Thanks to Andy Polyakov for chasing this down.

into nuts.ninka.net:/disk1/davem/BK/sparc-2.5

into nuts.ninka.net:/disk1/davem/BK/net-2.5

Use this to simplify 'finish_task_switch', but perhaps more
importantly we can use this to track down why some processes
seem to sometimes not die properly even after having been
marked as ZOMBIE. The "task->state" flags are too fluid to 
allow that well.

This fixes the generic __div64_32() to correctly handle divisions by
large 32-bit values (as used by nanosleep() and friends, for example).

It's a simple bit-at-a-time implementation with a reduction of the high
32-bits handled manually.  Architectures that can do 64/32-bit divisions
in hardware should implement their own more efficient versions.

 - add 'sched_clock'
 - delete smplock.h

The most important part is that it makes x86-64 compile again.
Without that 2.6 users won't be very happy.

It also works around a bug that allowed every user program to reboot the
system on B stepping K8.

Also update to match some recent i386 fixes.

Full ChangeLog:
 - Add acpi_pic_set_level_irq to make ACPI compile again
 - Work around compat mode K8 bug in IRET exception handling
 - Increase exception stack. The old 1k stack was too easy
   to overflow (from Jim Paradis, changed by me)
 - Replace safe_smp_processor_id with cpuid (needed for above)
 - When there is only one node always enable fake_node mode
 - Merge with i386 (NTP gettimeofday monoticity fix, irq nr_vectors change)
 - Fix compile problem for UP kernels in time/cpufreq
 - Set all nodes online at bootup
 - Define node_to_cpumask correctly

This documents the existence of a forth 'motioneye' camera plugged into
the USB bus, of course unsupported by the meye driver.

This corrects the Zoom and Thumbphrase button events.

The first FAT entry should have the media byte (0xf0,0xf8,...,0xff)
extended with all 1 bits in the first FAT entry.

Checking this is a good idea, it prevents us from mounting garbage
as FAT - there is no good magic for FAT.

Unfortunately, Windows does not enforce this, and 2.4 doesn't either.
It turns out that there are filesystems around (two reports so far) that
have a zero first FAT entry, and work under Windows and 2.4 but fail to
mount under 2.6.

So, this weakens the test.

The 0xfa code can be a key scancode or it can be a protocol scancode.

Only few keyboards use it as a key scancode, and if we always interpret
it as a protocol scancode then these rare keyboards will have a dead
key.  If we interpret it as a key scancode then we have a dead keyboard
in case it was protocol.

Clearly it is safer to prefer to interpret it as a protocol scancode.

This moves the test for ACK and NAK up, so that they are always seen as
protocol.

This is just a minimal patch.  What I did in 1.1.54 was to keep track of
commands sent with a flag reply_expected, so that 0xfa could be taken as
ACK when a reply is expected and as key scancode otherwise.  That is the
better solution, but requires larger surgery.

into home.osdl.org:/home/torvalds/v2.5/linux

into nuts.ninka.net:/disk1/davem/BK/net-2.5