Probably leftover of statically allocated urbs.

fix memory leak

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

Currently with 2.5, when I suspend and resume my powerbook, I find
that the USB subsystem no longer sees root hub events, i.e. it doesn't
notice when I plug in a new USB device (it doesn't notice when I
unplug a device either but of course the driver for the device sees
that it is no longer responding).

It turns out that what happens is that the root hub timer goes off
after the OHCI driver has done its suspend stuff.  The timer routine
sees that the HCD is not running at the moment and doesn't schedule
another timeout.  Hence the series of timeouts stops.

This patch exposes DMA addresses in URBs.  It exposes new APIs that
let drivers be a bit smarter in terms of DMA, reducing USB overhead
on some platforms (but not commodity pcs).  As discussed with DaveM,
and on the usb-devel list.

Supporting patches are still needed.  Of course, there's teaching HCDs
to use _these_ addresses when they're provided (easy).  There's also
teaching drivers (like hid) to use the new usb_buffer_alloc() support,;
can happen incrementally.  And adding scatterlist support, which will
be desirable for usb-storage and hpusbscanner.  But this is the start
needed to get all of that going.

This patch makes EHCI

  - Share the same TD queueing code for control, bulk,
    and interrupt traffic;
  - Queue interrupt transfers, modifying the code for
    urb submit/unlink/complete;
  - Thinner, by removing lots of nasty fatty special case
    logic for interrupt transfers (size, no queueing, etc);
  - Grow some "automagic resubmit" logic, ready to be
    ripped out soonish;
  - Package its interrupt scheduling so it can be called
    from more places.

This patch teaches the ehci driver how to dump its schedule
through two driverfs files:

  "sched-async" shows the control/bulk queue.  usually has
     no tds, often the idle queue head is showing.
  "sched-periodic" shows the iso/interrupt schedule.

Since this is for debugging, the files aren't normally
configured into the driver.

 - trivial: cache file->f_dentry->d_inode; saves a few bytes of compiled
   size.
 - move expand_stack inside ARCH_STACK_GROWSUP, add an alternate
   implementation for PA-RISC.
 - partially fix the comment (mmap_sem is held for READ, not for WRITE).
   It still doesn't make sense, saying we don't need to take the spinlock
   right before we take it.  I expect one of the vm hackers will know
   what the right thing is.

Testing of course revealed some bugs introduced during the cleanups,
so these are fixed here with a couple of other small bits, like improved
debugging code.

Things are indeed as conjectured, and I can reproduce the situation
where usb_string() returns -EPIPE. Now that this is an internal
error code for the USB subsystem, and not meant to get out to the
user, I made these driverfs files empty in case of error.
(While if there is no error but the string has length 0,
the file will consist of a single '\n'.)

One fewer random memory corruption. Unfortunately, there are more.

Andries

The recent "unlink cleanups" patch had a problem
with bitmask byteswapping.

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

into osdl.org:/home/mochel/src/kernel/devel/linux-2.5-driverfs

the ones that create the file.

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

This is invoked by mount -remount,resize=<blocks>.
See Documentation/filesystems/jfs.txt for more information.

This brain fart is left over from some cleanup of these functions a _long_ 
time ago. We need to dput() the dentry, since we have an implicit count of
one left over from the create function.

Instead, we were dput() on the directory that it was in, which we didn't 
have a matching dget() for. 

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

In order for JFS to be able to quiesce the current activity, while
blocking new transactions, the locking needed some rework.  New
transactions are stopped in the functions txBegin or txBeginAnon,
where the rdwrlock (IREAD_LOCK/IWRITE_LOCK) may be held.  Dirty
inodes may need to be committed while new transactions are blocked
here, so another lock is introduced (commit_sem) which is taken after
txBegin/txBeginAnon is called.  This ensures that the proper
serialization takes place, without the write_inode method needing to
grab the rdwrlock.

In addition, the use of IWRITE_LOCK and IREAD_LOCK has been removed
from directory inodes.  The serialization done by the VFS using i_sem
is sufficient to avoid races.

This patch removes JFS's dependency on down_write_trylock.

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

This patch is the first part of fixing the EHCI driver to queue
interrupt transactions, handle larger requests, and basically treat
interrupt as just "bulk that lives on the periodic schedule".  One
more patch should wrap that up.

     qh processing cleanup
	- split "append tds to qh" logic out of "put on async schedule",
	  so it can be used with "put on periodic schedule" too
     interrupt transfer cleanup
	- save rest of scheduling params in the qh
	- calculate scheduling params only once
     other cleanup
	- use new container_of()
	- minor code shrinkage (avoid pipe bitops, conditionals, etc)
	- rename variable (will track endpoints, not urbs)
	- free_config() logic

As requested by Adam Richter.

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

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

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

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

* fix spurious bad initializations
* pound phy a la SMSC's app note on the subject

occasional linker warnings/errors

* when you hit a memory shortage, also drop the packets on-board
* several KERN_xxx printk prefix corrections