Patch from Martin Bligh and Dave Hansen

If a PAE machine has 1G of memory and you set PAGE_OFFSET to 2G, the
kernel will only instantiate a PMD to cover the 2G-3G region.  But
another PMD is needed for the 3G-4G region for the APIC and possibly an
extended vmalloc region.

So the patch changes the code to instantiate PMDs out to the end of
physical memory.

It's a no-op for PAGE_OFFSET=3G, and _could_ be part of the
CONFIG_PAGE_OFFSET patch.  But it seems a reasonable generalisation
anyway.

Ancient patch From Bill Irwin

The patch is intended to show improved information about where the
memory went during OOM-killing events.

- when the OOM killer fails and the system panics, calls
  show_free_areas()

- reorganize show_free_areas() to use for_each_zone()

- add per-cpu stats to show_free_areas()

- tags output from show_free_areas() with node and zone information

fail_writepage() does not work.  Its activate_page() call cannot
activate the page because it is not on the LRU.

So perform that function (more efficiently) in the VM.  Remove
fail_writepage() and, if the filesystem does not implement
->writepage() then activate the page from shrink_list().

A special case is tmpfs, which does have a writepage, but which
sometimes wants to activate the pages anyway.  The most important case
is when there is no swap online and we don't want to keep all those
pages on the inactive list.  So just as a tmpfs special-case, allow
writepage() to return WRITEPAGE_ACTIVATE, and handle that in the VM.

Also, the whole idea of allowing ->writepage() to return -EAGAIN, and
handling that in the caller has been reverted.  If a writepage()
implementation wants to back out and not write the page, it must
redirty the page, unlock it and return zero.  (This is Hugh's preferred
way).

And remove the now-unneeded shmem_writepages() - shmem inodes are
marked as `memory backed' so it will not be called.

And remove the test for non-null ->writepage() in generic_file_mmap().
Memory-backed files _are_ mmappable, and they do not have a
writepage().  It just isn't called.

So the locking rules for writepage() are unchanged.  They are:

- Called with the page locked
- Returns with the page unlocked
- Must redirty the page itself if it wasn't all written.

But there is a new, special, hidden, undocumented, secret hack for
tmpfs: writepage may return WRITEPAGE_ACTIVATE to tell the VM to move
the page to the active list.  The page must be kept locked in this one
case.

There's nopoint in walking through a lot of tmpfs or ramdisk pages when
we're trying to clean memory.  So if a memory-backed inode is
discovered during writeback, skip the entire superblock.

Patch from Mark Fasheh <mark.fasheh@oracle.com> (plus a few cleanups
and a speedup from yours truly)

Adds the semtimedop() function - semop with a timeout.  Solaris has
this.  It's apparently worth a couple of percent to Oracle throughput
and given the simplicity, that is sufficient benefit for inclusion IMO.

This patch hooks up semtimedop() only for ia64 and ia32.

The pte_chain_unlock() needs to be outside the ifdef.

The read_zero() implementation for !CONFIG_MMU was very inefficient.
This sped-up version has been tested and acked by Greg Ungerer.

Back out the sys_syslog()-based printk-from-userspace and replace
it with Ben's /proc/kmsg version.

Requires a `mknod /dev/kmsg c 1 11'.

Patch from Robert Love <rml@tech9.net>

We can never get rid of it if we do not deprecate it - so do so and
print a stern warning to those who still run bdflush daemons.

The PF_MEMALLOC handling got broken somewhere, and it is now possible
for a PF_MEMALLOC process to reenter page reclaim.

Change it to fail the allocation if we're PF_MEMALLOC and there are
zero pages free.

This removes calls to function which disappeared during last Iphase
driver update.  Since this update, Iphase driver has been using plain
modern pci style init.

Problem wasn't noticed until Adrian Bunk tried to build non-modular kernel
(I only tested the modularized driver). Everybody else seemed happy :o)

scrup is using memcpy even when the memory areas src, dest overlap.  The
key is to use memmove which handles overlapping memory gracefully.

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

2.5 currently tries to register disk sda twice. Not nice and now we use
sysfs to do name to dev_t mapping, I couldnt mount my root filesystem.

This driver does not need to use atomic operations on local variables.

Trivial but annoying: two printk() calls in drivers/scsi/hosts.c are
missing '\n'

Also, for some reason I have not yet investigated, shost_tp->name is
NULL here.  This should not be, eh?  If it can be, we should do
something to tidy up the printing of it.

This error message is uber annoying and needs to go.  Non-root can flood
the console with this junk on invalid SCSI CD-ROM ioctl(), and that is
exactly what gnome-cd does.

An illegal ioctl() returns an error to the program.  That is sufficient
- we do not need KERN_ERROR warnings all over the place.  Especially
when any user can cause them at any rate.

In some configurations, parport and bttv request a module inside their
module_init function.  Drop the lock around mod->init(), change
module->live to module->state so we can detect modules which are in
init.

module-init-tools 0.9 and newer supply a replacement depmod, so
it's safe to run again.

Also, some external programs like PCMCIA and mkinitrd really want the
directory hierarchy in /lib/modules back again: it makes no difference
to the tools (since 0.9), so revert it.

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

Relatively straightforward fixes for intermezzo problems in 2.5.50.  I
think all of them related to:
 - two missing headers
 - use of timespec instead of time_t.

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

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

I made the changes to the set/get_registers code.

Cset exclude: rth@dorothy.sfbay.redhat.com|ChangeSet|20021207231352|30637

 - remove NATIVE_CHAR typedef
 - remove ACPI_{GET,VALID}_ADDRESS macros
 - fix memory corruption in deletion of a static AML buffer
 - fix fault caused by 0-length AML
 - fix user-buffer overwrite/corruption of buffer is too small
 - fix buffer-to-string conversion

This allowed a lock to be removed.
Also removed the MOD_* functions, and some remove logic was cleaned
up by Oliver Neukum.

into groveronline.com:/root/bk/linux-acpi

here is an id-patch to get the Sony Cybershot F717 6meg pixel digital
camera working with the standard usb-storage device driver.

Here are minimal usb_find_interface() patches for the core, usblp and
scanner.

Basic design is:
- device major (USB_MAJOR for now) and minor are stored in probe()
   function to struct usb_interface as kdev_t
- open() can use new core function usb_find_interface() to find matching
  device in drivers device list
- disconnect() will set kdev_t struct usb_interface to NODEV, so open
  wont open it anymore without new probe()

I tested these patches and they work for me. I will work on small patches
of other work in these drivers (like removal of lock_kernel/unlock_kernel
in usblp, fixing the disconnect problems in both drivers etc.). Those
patches would be very small too, but there will be quite many.

Thanks to Pat Mochel for pointing this out to me.

This patch disables the USB Bluetooth TTY driver (bluetty.o) from
the drivers/usb/class directory if the Linux Bluetooth subsystem
is selected.

The logic surrounding COMMIT_Holdlock was well-intentioned to reduce
latency when deleting files, but it can also result in a hang that I don't
have good fix for.  I don't think removing this will hurt our overall
performance very much.