This removes the cmpxchg from the PID allocator and replaces it with a
spinlock.  This spinlock is hit only a couple of times per bootup, so
it's not a performance issue.

Ulrich found another small detail wrt. POSIX requirements for threads -
this time it's the recursion features (read-held lock being write-locked
means an upgrade if the same 'process' is the owner, means a deadlock if a
different 'process').

this requirement even makes some sense - the group of threads who own a
lock really own all rights to the lock as well.

These changes fix this, all testcases pass now.  (inter-process
testcases as well, which are not affected by this patch.)

(SIGURG and SIGIO semantics should also continue to work - there's some
more stuff we can optimize with the new pidhash in this area, but that's
for later.)

The loop device driver was broken in 2.5.38 when it was converted over
to use gendisk.  I discovered this while doing final regression testing
on the ext3 htree code.

The problem is that figure_loop_size() is setting the capacity of the
loop device in kilobytes (because that's what compute_loop_size()
returns), but set_capacity() expects the size in 512 byte sectors.

I've enclosed a patch which fixes the problem, as well as simplifying
the code by eliminating compute_loop_size(), since it is a static
function is only used once by figure_loop_size().

into kleikamp.austin.ibm.com:/home/shaggy/bk/jfs-2.5

As it is at the moment, sys_mprotect will dereference a null pointer
if you use it on a region that is contained within the first vma.  I
have a little program that demonstrates this (I'll post it if anyone
is interested).  What happens then is that the process hangs in
do_page_fault at the down_read on the mm->mmap_sem, since sys_mprotect
has done a down_write on mm->mmap_sem.

The problem is that mprotect_fixup isn't updating prev properly.  Thus
we can finish the main loop in sys_mprotect with prev == NULL.  This
has been the case since Christoph's cleanups went in.  Prior to that,
mprotect_fixup always set prev to something non-NULL.  I suspect that
not updating prev could also cause vmas to get dropped completely if
the region being mprotected spans more than one vma.

The patch below fixes the problem by making mprotect_fixup set prev to
a reasonable value in all circumstances.

This unsafe access to per-CPU data via reordering of instructions or use
of "get_cpu()".

Before anyone balks at the brlock.h fix, note this was in the
alternative version of the code which is not used by default.

Before the irqs_disabled() check in preempt_schedule(), we worked around
some locking issues in slab.c.  Now that we will never preempt with
interrupts disabled, we can remove those and clean things up.

This is courtesy of Manfred Spraul.

This converts the debugging check in do_exit from a check on
preempt_count() to in_atomic().

The main benefit to this is we will stop warning over the BKL and now
use the standard mechanism for such checks.

Looks like I dropped a hunk from my patchset, sorry.

We never set FL_SLEEP in the flock case, so if we should block, we'll
livelock instead.

This is needed for reasonable read latency with the new VM
behaviour. 

NOTE! This is way too unfair, Andrew and Jens are working on
alternatives.

 - Makefile cleanups and fixes
 - a bunch of syscalls added
 - removed crap from asm/ide.h (it's not needed anymore)
 - __down_read_trylock fix

IDE must use blk_queue_empty() and not do a list_empty() on the
(potentially only) dispatch queue.  This took quite a while to find
while debugging a new io scheduler...

This fixes the emacs bug reported by Andries.  It should probably also
fix other, terminal handling related weirdnesses introduced by the new
PID handling code in 2.5.38.

The bug was in the session_of_pgrp() function, if no proper session is
found in the process group then we must take the session ID from the
process that has pgrp PID (which does not necesserily have to be part of
the pgrp).  The fallback code is only triggered when no process in the
process group has a valid session - besides being faster, this also
matches the old implementation.

[ hey, who needs a POSIX conformance testsuite when we have emacs! ;) ]

The direct-IO code is currently generating 1 meg BIOs (and
subsequent BUGs) because it doesn't know about bio_add_page().

Could we please drop it to 16k until we get it sorted out?

into kroah.com:/home/greg/linux/BK/gregkh-2.5

-increased timeout value because some people reported problems
-(important!) Vender ID has changed from 0x1212 to 0x10D2 , my official
  assigned one.
-added usblcd driver to configure.help

Update to full working driver status. Latest firmware 4.06 too. Driver
now officially supported.

Based off of a patch from Stuart MacDonald <stuartm@connecttech.com>

This cleans up the error path in the open() call to make a bit more
sense.

This fixes a stupid error in the timeout value when downloading firmware
to a device.  The WhiteHEAT device now works properly with this patch.

Like the header says, this patch fixes up the various Transfer- and
Transport-level return codes.  There were a lot of places in the various
subdrivers that were not particularly careful about distinguishing the
two; it would help if the people currently maintaining those drivers could
take a look at my changes to make sure I haven't screwed anything up.

# Converted US_BULK_TRANSFER_xxx to USB_STOR_XFER_xxx, to make it more
# easily distinguishable from USB_STOR_TRANSPORT_xxx.  (Also, in the
# future these codes may apply to control transfers as well as to bulk
# transfers.)
#
# Changed USB_STOR_XFER_FAILED to USB_STOR_XFER_ERROR, since it implies
# a transport error rather than a transport failure.
#
# Added a USB_STOR_XFER_STALLED code, to indicate a transfer that was
# terminated by an endpoint stall.

This patch is in preparation for one in which usb_stor_transfer_partial()
and usb_stor_transfer() are replaced by usb_stor_bulk_transfer_buf() and
usb_stor_bulk_transfer_srb() respectively, with slightly different
argument lists.  Ultimately the subdrivers will be able to use these
routines in place of the slightly specialized versions they have now and
in place of the ones in raw_bulk.c.

compile fails with the following message:

	> In file included from ohci-hcd.c:136:
	> ohci-dbg.c:318: parse error
	> make[3]: *** [ohci-hcd.o] Error 1

due to a missing #include <linux/version.h>

Here is a trivial patch for this.

is it guarenteed that callers have zero'd out the device
before this is invoked?  Else the following is necessary to
prevent potential OOPS's derefencing interface->dev.driver in
the generic device layer.

Here's an EHCI update, I'll send separate patches to sync 2.4 with
this version.  Changes in this version include:

  - An earlier locking update would give trouble on SPARC, where
    irqsave "flags" aren't flags.  This resolves that issue by
    adding a module parameter to limit work done with irqs off.
    (Some net drivers do the same thing.)

  - Optionally (now #ifdef DEBUG) collects some statistics on IRQs
    and URBs.  There are more IAA interrupts than I want to see,
    during extended usb-storage loading.

  - Adds a commented-out workaround for a problem I've seen on one
    VT8235.  Seems likely an issue with this specific motherboard;
    another tester hasn't reported such issues.

  - Includes the jiffies time_after() patch from Tim Schmielau.

  - Minor tweaks to the hcd portability (get rid of another #if).

  - Minor doc/diagnostic/... updates

This USB patch updates the OHCI driver:

  - converts to relying on td_list shadowing the hardware's
    schedule; only collecting the donelist needs dma_to_td(),
    and td list handling works much like EHCI or UHCI.

  - leaves faulted endpoint queues (bulk/intr) disabled until
    the relevant drivers had a chance to clean up.

  - fixes minor bugs (unreported) in the affected code:
      * byteswap problem when unlinking urbs ... symptom would
        be data toggle confusion (since 2.4.2x) on big-endian cpus
      * latent bug if folk unlinked queue in LIFO order, not FIFO

  - removes unnecessary debug code; mostly de-BUG()ged

The interesting fix is the "leave queues halted" one.  As
discussed on email a while back, this HCD fault handling
policy (also followed by EHCI) is sufficient to let device
drivers implement the two key fault handling policies that
seem to be necessary:

    (a) Datagram style, where issues on one I/O won't affect
        the next unless the device halted the endpoint.  The
        device driver can ignore most errors other than -EPIPE.

    (b) Stream style, where for example it'd be wrong to ever
        let block N+1 overwrite block N on the disk.  Once
        the first URB fails, the rest would just be unlinked
        in the completion handler.

As a consequence of using the td_list, you can now see urb
queuing in action in the driverfs 'async' file.  At least, if
you look at the right time, or use drivers (networking, etc)
that queue (bulk) reads for a long time.

In certain situations, dbNextAG set db_agpref to db_numag, with is
one higher than the last valid value.  This will eventually result in
a trap.

This fixes all xchg()'s and a preemption bug.

This does the following things:

 - removes the ->thread_group list and uses a new PIDTYPE_TGID pid class
   to handle thread groups. This cleans up lots of code in signal.c and
   elsewhere.

 - fixes sys_execve() if a non-leader thread calls it. (2.5.38 crashed in
   this case.)

 - renames list_for_each_noprefetch to __list_for_each.

 - cleans up delayed-leader parent notification.

 - introduces link_pid() to optimize PIDTYPE_TGID installation in the
   thread-group case.

I've tested the patch with a number of threaded and non-threaded
workloads, and it works just fine. Compiles & boots on UP and SMP x86.

The session/pgrp bugs reported to lkml are probably still open, they are
the next on my todo - now that we have a clean pidhash architecture they
should be easier to fix.

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

T30_s * is part of a union, so the typedef needs to exist even when
CONFIG_ISDN_TTY_FAX is not set.

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

When converting all L_TARGETs to lib.a, I missed these instances.

Update alpha port to work with new nanosecond xtime, and the in_atomic()
requirements.

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

The problem is that the local APIC code references stuff in
mpparse, but 2.5.37 changed arch/i386/kernel/Makefile to only
compile mpparse for SMP.

This patch works around this by enforcing CONFIG_X86_MPPARSE
for all LOCAL_APIC-enabled configs.

Add bio_get_nr_vecs(). It returns an approximate number of pages that
can be added to a block device. It's just a ballpark number, but I think
this is quite fine for the type of thing it is needed for: mpage etc
need to know an approx size of a bio that they need to allocate. It
would be silly to continously allocate 64-page sized bio_vec entries, if
the target cannot do more than 8, for example.