pci_hotplug_core that got it implicitly before.

ntfs that got it implicitly before.

jffs2 that got it implicitly before.

intermezzo that got it implicitly before.

hugetlbfs that got it implicitly before.

cifs that got it implicitly before.

quota that got it implicitly before.

drivers/base relies on device.h pulling in sched.h pulling in the rest
of the world.  Add some explicit dependencies in preparation for removing
sched.h from device.h.

coda_linux simply doesn't need sched.h

elf.h simply doesn't need sched.h

ftape.h really wants interrupt.h, not sched.h

i2c.h simply doesn't need sched.h

if_pppox simply doesn't need sched.h

NFSD users that got it implicitly before.

mmuless ports don't need dup_mmap nor allocation of a pgd.

I tried to avoid ifdef-mess as far as possible, and to archive that
I created small wrappers for pgd allocation/freeing and move taking
of the mmap semaphore into dup_mmap from the only caller.  The end
result is just one additiona ifdef.

It's only need for the two monster-inlines set_fs_root and set_fs_pwd
that should better be out of line anyway.  Some additional cleanup like
named initializers as extra bonus.

Once again we only need a forward-declaration of struct vfsmount.

This is a preparation to get rid of the implicit includes in
dcache.h and fs_struct.h.

Remove four dead prototypes and don't include mount.h here - fs.h
itself doesn't need it at all (just the struct vfsmount forward
declaration) and gets it through dcache.h anyway.

This removes the pci_dev "->name[]" field, and makes users use the
"struct device" name field instead.

It also trimps it down to 50 bytes and limited the length of the vendor
& device descriptions to 20 bytes each.  Now we have three cases:

 - unknown vendor & unknown device -> "PCI device %04x:%04x".
	Clearly limited to 21 chars.
 - known vendor, unknown device -> "PCI device %04x:%04x (%.20s)"
	24 + 20 chars
 - known vendor, known device -> "%.20s %.20s"
	20 + 1 + 20 + 1, EXCEPT:
 - multiple devices of the same type add " (#%d)"
	so 42 + 4 + 4 = 50.  This is the point where an IBMer tells me they
	intend to sell a machine with > 9999 PCI devices of the same type ;-)

This limits the PCI IDs to a reasonable amount of space.

For release, I think we do want to go back up to 80 for prettier output

parport only needs jiffies.h, not sched.h

nfsd/cache.h doesn't need sched.h, just sockaddr_in and iovec

input.h wants fs.h and timer.h, not sched.h

atmdev.h only wants wait.h, not sched.h

blkdev.h simply doesn't need sched.h

The inode reclaim is too aggressive at present - it is causing the
shootdown of lots of recently-used pagecache.  Simple testcase: run a
huge `dd' while running a concurrent `watch -n1 cat /proc/meminfo'.
The program text for `cat' gets loaded from disk once per second.

This is in fact because the dentry_unused reclaim is too aggressive.

(The general approach to inode reclaim is that it _not_ happen at the
inode level.  All the aging and lru activity happens at the dcache
level.)

The problem is partly due to a bug: shrink_dcache_memory() is returning
the *total* number of dentries to the VM, rather than the number of
unused dentries.

This patch fixes that, and goes a little further.

We do want to keep some unused dentries around.  Reclaiming the last
few thousand dentries is pretty pointless, and will allow reclaim of
the last few thousand inodes and their attached pagecache.

So the algorithm I have used is to not allow the number of unused
dentries to fall below the number of used ones.  This keeps a
reasonable number of dentries in cache while providing a level of
scaling to the system size and the current system activity.

(Magic number alert: why not pin nr_unused to seven times nr_used,
rather than one times??)

shrink_dcache_memory() has been changed to tell the VM that the number
of shrinkable dentries is:

	zero if (nr_unused < nr_used)
	otherwise (nr_unused - nr_used)

so when there is memory pressure the VM will prune the unused dentry
cache down to the size of the used dentry cache, but not below that.

The patch also arranges (awkwardly) for all modifications of
dentry_stat.nr_dentry to occur inside dcache_lock - it was racy.

Replace some kmaps in mpage.c with kmap_atomic.

Stephen Tweedie reports a 2.4.7 problem in which kswapd is chewing lots
of CPU trying to reclaim inodes which are pinned by buffer_heads at
i_dirty_buffers.

This can only happen when there's memory pressure on ZONE_HIGHMEM - the
2.4 kernel runs shrink_icache_memory in that case as well.  But there's
no reclaim pressure on ZONE_NORMAL so the VM is never running
try_to_free_buffers() against the ZONE_NORMAL buffers which are pinning
the inodes.

The 2.5 kernel also runs the slab shrinkers in response to ZONE_HIGHMEM
pressure.  This may be wrong - still thinking about that.

This patch arranges for prune_icache to try to remove the inode's buffers
when the inode is to be reclaimed.

It also changes inode_has_buffers() and the other inode-buffer-list
functions to look at inode->i_data, not inode->i_mapping.  The latter
was wrong.

slab does various consistency checks during `cat /proc/slabinfo'
processing.  If it finds one it stupidly goes BUG just before
displaying the info which is required to diagnose the bug.

Change it to not go BUG, but to emit some useful printks and continue.

The patch also removes an uninteresting printk from the boot process.

Patch from Rohit Seth, changelog from Bill Irwin:

(1) fixes failure to clear key->busy (yes, it's always under a lock)
(2) fixes key->count being unconditionally set to 1 in alloc_key()
(3) reduces search to key->size >> HPAGE_SHIFT from key->size
(4) actually uses vma->vm_private_data to release the key as intended

plus the cleanup:
(5) removes the int *new argument to alloc_key()

A rollup of Bill's 11-patch series which replaces hugetlb's custom
inode with a bare radix tree.  Reviewed and acked by Rohit.

- revert doublefreeing patch

- Put set_new_inode() and the inode allocation loop into an
  alloc_key(), and introduce a new opaque type "struct hugetlb_key".

- Wrap the release path in alloc_shared_hugetlb_pages() with a
  release_key() function that handles the release.

- Wrap hugetlb_prefault() with prefault_key() in order to isolate the
  dependency on inodes for prefaulting the hugetlb vma.

- Replaces the usage of inode->i_writecount as a flag marking keys
  busy with a boolean flag field in struct htlbpagekey, and removes the
  last dependency of alloc_shared_hugetlb_pages() on struct inode.

- Remove the last direct usage of struct inode within the hugetlb
  functions.

- Removes many direct usages of struct inode within the key
  manipulation API in exchange for passing references to the key
  structure itself.

- Expand out prefault_key() into its hugetlb_prefault() component,
  but substitute stubs to abstract out inode access.

- Move uid/gid/mode/size fields used in struct inode and the checks
  on them into key management code and structures.

- Substitute direct usage of radix trees for inodes, and removes the
  custom-allocated inodes.

- Wrap up the release path by adding proper refcounting of keys.

- add init_timer in bttv driver

- remove duplicated init_timer() in ncpfs.

- remove noisy printk's from 3c59x.c

- sparc64 compile fix with CONFIG_HUGETLBPAGE=y - htlbpage_max is now an
  int

Patch from Hugh Dickins <hugh@veritas.com>

tmpfs failed fsx+swapout tests after many hours, a page found zeroed.
Not a truncate problem, but mirror image of earlier truncate problems:
swap goes through mpage_writepages, which must therefore allow for a
sudden swizzle back to file identity.

Second time this caught us, so I've audited the tree for other places
which might be surprised by such swizzling.  The only others I found
were (perhaps) in the parisc and sparc64 flush_dcache_page called
from do_generic_mapping_read on a looped tmpfs file which is also
mmapped; but that's a very marginal case, I wanted to understand it
better before making any edit, and now realize that hch's sendfile
in loop eliminates it (now go through do_shmem_file_read instead:
similar but crucially this locks the page when raising its count,
which is enough to keep vmscan from interfering).

Patch from Hugh Dickins <hugh@veritas.com>

swap_readpage and swap_writepage forgot
to unlock_page if get_swap_bio failed.

Patch from Hugh Dickins <hugh@veritas.com>

On some architectures (cachetlb.txt gives HyperSparc as an example)
it is essential to flush_cache_page while pte is still valid: the
rmap VM diverged from the base 2.4 VM before that fix was made,
so this error has crept back into 2.5.

Patch below applies to 2.5.47 or 2.5.47-mm1 - needs more work over
shared pagetables, but they've silently fallen out of 2.5.47-mm1:
oversight?  I'll send Alan the equivalent for 2.4-ac shortly.

(I wonder, what happens if userspace now modifies the page
after the flush_cache_page, before the pte is invalidated?)

Patch from Andreas Gruenbacher <agruen@suse.de>

Add a gfp_mask parameter to the free() callback so that the callback can
safely do I/O, etc. The free callback can now also fail.  This will be
needed by reiserfs.

The order of entries on the cache entry lru is reversed so that
list_for_each_safe() can be used. Several helper functions that don't
make the code any better are removed. Finally, a couple of cosmetic
things.

From Badari.

bio_add_page returns zero on failure - we need to propagate that
to the dio_bio_add_page() caller.

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