Several file systems in tree that nominally support files >2GB set their
s_maxbytes value to ~0ULL. This has the nasty side effect on 32bit machines
that when a file write reaches the page cache limit (e.g. 2^43) it'll silently
wrap and destroy data at the beginning of the file.

This patch changes the file systems in question to fill in a proper limit.

I also have an alternate patch that adds a check for this generically
in super.c, but preliminary comments from Al suggested that he prefered
to do it in the file systems, so it is done this way way.

The default for NR_FILES of 8192 is far too low for many workloads. This
patch does dynamic sizing for it instead. It assumes file+inode+dentry
are roughly 1K and will use upto 10% of the memory for it.

Also removes two obsolete prototypes.

This patch speeds the bootmem freeing up a bit. Not particularly important,
but helps on some slow simulators where the loop can chew up significant
CPU time.

Hallo Linus,

This is the slab name cleanup you originally requested when the reiserfs
slab name too long boot bug was introduced. It replaces the static
name limit for slab cache names with the requirement for the caller
to supply a stable name. This version addresses all concerns that were given
over earlier versions of the patch.

As I do not feel very strongly about the slab cache name limit and you
also do not seem to be interested in it and the original bug of reiserfs
not booting anymore has been long fixed in your tree with the patch
you originally rejected from me I will not resend this patch after this
try.

Patch against 2.5.4pre1.

-Andi

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

into soap.kroah.net:/home/greg/linux/bk_main/usb-3

into soap.kroah.net:/home/greg/linux/bk_main/usb-2

Patch done by Oliver Neukum.

Some driver changes were done by Oliver Neukum and David Brownell.

These changes have been approved by the CRIS maintainer.

	- add mem_flags support
	- portions of this patch by Oliver Neukum and David Brownell.

	- initial add of the "int mem_flags" call to the usb_submit_urb() call

  	- Updates the documentation
  	- Adds Veo Stingray support
  	- Fixes hotplug table dependency upon now-defunct symbol
  	- deletes drivers/usb/ibmcam.h

  	- Code-Review from Oliver Neukum: remove SMP races.
  	- Added some wake_up calls after auerbuf_releasebuf to wake up tasks waiting
  	  for cp buffers.
  	- Change the module count handling to automatic (owner: THIS_MODULE).

  Al Viro: fix a typo (destory->destroy)

   This is hopefully last bugfix for a bug introduced by struct inode splitting.
   Because of setting i_flags to some value and then cleaning the i_flags
   contents later, on-disk items received wrong item version ob v3.6 filesystems

	Kudos to OGAWA Hirofumi for finding that one - gcc barfs on the
current code, trying to define an alias to external symbol.

	hpux_getdents() contains a years-old copy of code from fs/readdir.c.
Switched to use of vfs_readdir(), which does correct locking.

	Yet another flag/wait_queue pair bites the dust - hfs bitmap_{lock,wait}
was trying to implement a semaphore.

	Useless (lock,waitqueue) pair killed - we have fs-wide
exclusion between renames enforced by VFS, so hfs rename_{lock,wait}
can be removed.

	Pair (flag, wait_queue) in hpfs replaced with semaphore.

The previous patch did not provide protection for device lseek methods
(drivers/* stuff).  This patch pushes the BKL into each of the remaining
lseek methods -- without them we have a race.

I'd much prefer to have a a better lock to push down than the BKL, but
that will have to wait.

Before you balk at the size, remember patch #2 in this series which
removed much code ;-)

Thanks to Al for assistance, especially a listing of affected files.

	Robert Love

This is the second patch of three implementing further llseek cleanups,
against 2.5.4-pre1.  It does not depend on the other patches.

This patch cleans up various code and quite nicely removes much more
code than it adds.  Specifically:

- remove static lseek method which merely reimplements
  the standard no_llseek in the following seven files:
  hci_vhci.c, ite8172.c, nec_vrc5477.c, auerswald.c,
  pipe.c, netlink_dev.c, and socket.c

- remove fs/ufs/file.c::ufs_file_lseek -- Al says it is
  reimplementing generic_file_llseek, so let's use that
  instead (the comment about 32-bit sizes shouldn't be
  an issue, the generic method checks size)

- include smp_lock.h in 3 files missed from previous
  'remove bkl' patch

- Documentation/filesystem/Locking update

Please, apply.

	Robert Love

This is the first of three patches implementing further llseek cleanup,
against 2.5.4-pre1.

The 'push locking into llseek methods' patch was integrated into 2.5.3.
The networking filesystems, however, do not protect i_size and can not
rely on the inode semaphore used in generic_file_llseek.

This patch implements a remote_llseek method, which is basically the
pre-2.5.3 version of generic_file_llseek.  Locking is done via the BKL.
When we have a saner locking system in place, we can push it into this
function in lieu.

Ncpfs, nfs, and smbfs have been converted to use this new llseek.

Note this is updated over the previous posted patch.

	Robert Love

ia64: switched from sys_new*stat() to vfs_*stat() and cleaned up. 

solaris: switched from sys_new*stat() to vfs_*stat() and cleaned up. 
Missing LFS check added. 

irix_...() switched from sys_new*stat() to vfs_*stat() and cleaned up. 
Missing LFS check added

stat(2) variants in arch/* that used to copy inode fields manually
switched to vfs_*stat() and partially cleaned up

	added new helpers - vfs_stat(), vfs_lstat() and vfs_fstat().
	fs/stat.c switched to use them.

Following patches will

	stat(2) variants in arch/* that used to copy inode fields manually
	switched to vfs_*stat() and partially cleaned up

	irix_...() switched from sys_new*stat() to vfs_*stat() and cleaned
	up.  Missing LFS check added.

	similar for solaris ones

	ditto for x86 compatibility ones on ia64.

We are almost ready to switch to ->getattr() - let filesystem decide what
values should go into ->st_... (e.g. for CODA life would become much
easier if it could just use ->i_size of caching file, for supermount
we want ->i_ino inherited from underlying fs, etc.)

Another thing that needs to be done is fixing the rest of LFS/uid size
fsckups in architecture-specific variants of stat() - I've fixed several,
but quite a few are still there.

	procfs switched to alloc_inode/destroy_inode.

	more inode->u trimming - socket_i is killed.

During the course of developing our pthread library (the NGPT pthread
library) it became clear we needed some kernel support for handling
signals.  This patch helps the library by redirecting all signals sent
to tasks in a thread group to the thread group leader.  It also defines
the tkill() system call so the library can signal a specific task if
necessary. 

Given that as far as I know NGPT is the only user of thread groups, and
that this change would benefit any other user of thread groups, I'm
submitting this for inclusion in the 2.5 kernel.

Note that this patch also adds support for sys_gettid() for the
architectures that don't have it.  While this could have been split into a
spearate patch, it would create conflicts since this patch also adds
sys_tkill(), so I felt it was cleaner to leave them together.

Dave McCracken

======================================================================
Dave McCracken          IBM Linux Base Kernel Team      1-512-838-3059
dmccr@us.ibm.com                                        T/L   678-3059

  update

  Update version

The patch moves:

	* joystick drivers from drivers/char/joystick to drivers/input/joystick
	* gameport drivers from drivers/char/joystick to drivers/input/gameport
	* serio drivers from drivers/char/joystick to drivers/input/serio

I don't think the joystick drivers should stay in char, because they're
NOT character device drivers (check for register_chrdev, none to be found).

It also fixes build problems with sound driver gameport support.

the appended patch works around a bug in the PLX9050 chip. This chip is
used in various PCI ISDN adapters (it's an PCI interface chip) and has
an erratum when the BAR 0/1 has bit 7 set (the size of the region is
0x80, so aligning it to 0x80 is legal and really happens for people).

This workaround has been tested by a user who hit this problem with a
Gazel card. Basically the same fix has been done for Elsa cards, but it's
untested.

the appended patch fixes a problem where the ->rcvidx variable was not
initialized properly.

the appended patch fixes a case of undefined behavior, found by
Urs Thuermann and "VDA".