From Dominik Brodowski.

- Can simplify, since the policy is already known, and we only need to kick
  the CPU.

- Make sure we set the right method in the sysdev driver.

We don't need to protect against multiple suspend calls, since subsequent
ones will happen on an empty (or at worst - short) list.

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

Calls were moved to the PM core, so they must be compiled in to use them.

- Didn't realize that mount_root_failed_msg() had been removed, so it was 
  accidentally merged back in. It's gone again now, as well as the entire
  (unused) dmi_dump_system() function. 

Dan hasn't been maintaining cramfs for some time.

Mark it orphan until somebody else takes it up.

- Revert names of functions back to device_{suspend,resume} since at least 
  APM are still using them.

into home.osdl.org:/home/torvalds/v2.5/linux

This removes the pointless cramfs message when booting with cramfs
compiled in but not as the root filesystem.

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

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

 * makes the three USB drivers not use the procfs stuff, also added a
   warning that they should converted to sysfs.
 * Removes the leftover, obsolete VIDEO_PROC_FS config option, that
   should catch any other build failures too (if any).

static unconditionally, to allow multiple built-in modules.

From: Suparna Bhattacharya <suparna@in.ibm.com>

The /proc code's bare atomic_inc(&mm->count) is racy against __exit_mm()'s
mmput() on another CPU: it calls mmput() outside task_lock(tsk), and
task_lock() isn't appropriate locking anyway.

So what happens is:

	CPU0			          CPU1

      mmput()
      ->atomic_dec_and_lock(mm->mm_users)
                                          atomic_inc(mm->mm_users)
      ->list_del(mm->mmlist)
                                          mmput()
                                          ->atomic_dec_and_lock(mm->mm_users)
                                          ->list_del(mm->mmlist)

And the double list_del() of course goes splat.

So we use mmlist_lock to synchronise these steps.

The patch implements a new mmgrab() routine which increments mm_users only if
the mm isn't already going away.  Changes get_task_mm() and proc_pid_stat()
to call mmgrab() instead of a direct atomic_inc(&mm->mm_users).

Hugh, there's some cruft in swapoff which looks like it should be using
mmgrab()...

From: Dave Hansen <haveblue@us.ibm.com>

Hmmm.  This is looking like fallout from the massive wli-bomb.  Here's
the loop that controls the cpu booting, before and after cpumask_t:

-	for (bit = 0; kicked < NR_CPUS && bit < BITS_PER_LONG; bit++)
+	for (bit = 0; kicked < NR_CPUS && bit < MAX_APICS; bit++)
		apicid = cpu_present_to_apicid(bit);

"kicked" only gets incremented for CPUs that were successfully booted,
so it doesn't help terminate the loop much.  MAX_APICS is 256 on summit,
which is *MUCH* bigger than BITS_PER_LONG.
cpu_2_logical_apicid[NR_CPUS] which is referenced from
cpu_present_to_apicid() is getting referenced up to MAX_APICs, which is
bigger than NR_CPUS.  Overflow.  Bang.  garbage != BAD_APICID :)

From: Emilio Gallego Arias <egallego@telefonica.net>

Apparently a couple of files now need io_apic.h.

apm.c (at least) needs these.

From: chrisl@vmware.com

Fixes the "perl installer weirdness" problem which a few people have been
reporting.

The bug is triggered by creating the index.  Coping out the index we assume
the dirents start with the first entry after "." "..".

It can make the first previous deleted entry reappear.  In the past we set
inode to zero for an empty entry so this is not a problem.  That is not
true any more.

Also, there were a few places where we were altering inode times after
running ext3_mark_inode_dirty().  We should be doing that beforehand.

dmi_dump_system() is only used if CONFIG_ACPI_BOOT.

From: Matthew Wilcox <willy@debian.org>

Here's an update to Documentation/filesystems/Locking.

A `cat /dev/kmem' oopses the kernel.  This is because new Intel
copy_to_user() doesn't handle segfaults against the kernel-side source
address of the copy.

It is not obvious how to fix read_kmem(), and handling faults on either
source or dest is traditional behaviour, so fix it in the copy function by
adding exception table entries for the reads as well as the writes.

From: Francois Romieu <romieu@fr.zoreil.com>

Recent MOD_{INC/DEC}_USE_COUNT removal missed a MOD_DEC_USE_COUNT.

From: Francois Romieu <romieu@fr.zoreil.com>

- silly indentation;
- let's be more user-friendly with manufacturer specific (mis)feature:
  + s/CONFIG_DSCC4_CLOCK_ON_TWO_PORTS_ONLY/CONFIG_DSCC4_PCISYNC/
  + KConfig adequate entry
- broken warning message.

From: Francois Romieu <romieu@fr.zoreil.com>

CCR1 register voodoo: asic handles itself the flow control.

From: Francois Romieu <romieu@fr.zoreil.com>

Workaround for lack of true reset:
- devices/ports are put in silent mode at ifconfig down time but some
  state is kept around to allow 'ifconfig up' issuing at a later time.
  Device specific structures are allocated when the pci asic is
  probed: dscc4_init_ring() moves from dscc4_open() to dscc4_found1().
- try to use reset related board-specific feature at module removal
  time if available. Comments in the code explain the whole story.
  Not a complicated feature but it is unavailable on the cards I own
  and no user gave me feedback -> currently untested.
  It shouldn't harm anyway.

From: Francois Romieu <romieu@fr.zoreil.com>

- more #define for specific bits;
- more scc_patchl use;
- just say no to bozo programming:
  + SCC core _really_ disabled at startup;
  + Interrupts Mask Register setup and SCC core activation are
    done as late as possible (i.e. in dscc4_open());
  + they are reverted if dscc4_open() fails;
  + as well as unconditionnaly in dscc4_close();
- more or less paranoid quirk in Xpr handler.

From: Francois Romieu <romieu@fr.zoreil.com>

More conditional debug messages.

From: Francois Romieu <romieu@fr.zoreil.com>

Clock modes on dscc4 are feature-rich enough to deserve some explanation.

From: Francois Romieu <romieu@fr.zoreil.com>

Short comments so I can figure why things are done this way.

opl3sa2 forgot to initialise the spinlock.

From: NeilBrown <neilb@cse.unsw.edu.au>

The blockdev layer has a concept of 'claiming' a device, so for example it
can be claimed when a filesystem is mounted or when it is included into a
raid array.  Only one subsystem can claim it at a time.

This patch matches this functionality available to user-space via the
O_EXCL flag to open.

This allows user-space programs to easily test if a device is currently
mounted etc, and to prevent a device from being mounted or otherwise
claimed.

From: NeilBrown <neilb@cse.unsw.edu.au>

Current devices can be 'claimed' by filesystems (when mounting) or
md/raid (when being included in an array) or 'raw' or ....
This stop concurrent access by these systems.

However it is still possible for one system to claim the whole device
and a second system to claim one partition, which is not good.

With this patch, when a partition is claimed, the whole device is 
claimed for partitioning.  So you cannot have a partition and the
whole devices claimed at the same time (except if the whole device
is claimed for partitioning).