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

into nuts.ninka.net:/home/davem/src/BK/net-2.5

Check if DAD does not have source link-layer address option;
RFC2461 7.1.1.

Check if DAD is destined for solicited node multicast address
as RFC2461 required.

These patches fix ip multicast route (ipmr) on 2.5.73.

1 - Trivial C99 initialization
2 - Change functions/variables to static
3 - Drop and reacquire RTNL in error path
4 - Use time_after()
5 - Use alloc_netdev
6 - Fix OOPS on dropped packets
7 - Get rid of skb_linearize

Tested on 8-way SMP by bringing up pimd.

into osdl.org:/home/jmorris/bk/net/work-2.5

[Pointed out by Bjorn Helgaas via Arun Sharma]

This fixes an obvious cut and paste error in my original patch.

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

Needs more testing, especially in x8 mode.

Noticed by Marcelo Penna Guerra.

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

From Dominik Brodowski.

Add support for newest "Mobile Pentium 4-M" and the new "Mobile Pentium 4 with
533 MHz FSB" processors.

From Dominik Brodowski.

- separate functions which might be useful for speedstep-piix4,
  speedstep-via or speedstep-bios into a new speedstep-lib.c.
- clean up speedstep-ich as it will only be used for ICH-based chipsets
  in future.   
- remove now-obsolete speedstep_coppermine parameter

into tetrachloride.(none):/mnt/raid/src/kernel/2.5/cpufreq

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

s/GetConfiguration/GetConfigurationInfo/

From: Jan Dittmer <j.dittmer@portrix.net>

This adds an export for flush_tlb_all to i386_ksyms.c.  The drm modules
miss this, when compiling for SMP.

I changed Jan's patch to use EXPORT_SYMBOL_GPL.

From: Alex Tomas <bzzz@tmi.comex.ru>

Don't set the directory's index flag until we know that we're doing ahead
with the directory modification.

From: Geert Uytterhoeven <geert@linux-m68k.org>

NCR53C9x SCSI: Fix compilation after breakage in 2.5.71

From: Andrey Panin <pazke@donpac.ru>

this trivial patch changes mailing list address for visws subarch support
along with some occurences of my old email addresses.

We need to unconditionally brelse() the buffer in there, because
journal_remove_journal_head() leaves a ref behind.

release_buffer_page() does that.  Call it all the time because we can usually
strip the buffers and free the page even if it was not marked buffer_freed().

Mainly affects data=journal mode

ext3_block_truncate_page() is calling grab_cache_page() inside a JBD
transaction.  This is wrong, because transactions nest inside lock_page().

The deadlock is against shrink_list->ext3_journalled_writepage->journal_start.

This was not noticed before because we never used to journal writepage() data
in journalled-data mode.  And because the deadlock against
generic_file_write() is covered up by i_sem.

Rework things so that we lock the page prior to starting a transaction.

From: David Mosberger <davidm@napali.hpl.hp.com>

compat_sys_old_getrlimit() depends on sys_old_getrlimit() and the patch
below updates the guarding #ifdef accordingly.

From: Andrew Theurer <habanero@us.ibm.com>

This patch ensures that when node loads are compared, the load value is
normalised.  Without this, load balance across nodes of dissimilar cpu
counts can cause unfairness and sometimes lower overall performance.

For example, a 2 node system with 4 cpus in the first node and 2 cpus in
the second.  A workload with 6 running tasks would have 3 tasks running on
one node and 3 on the other, leaving one cpu idle in the first node and two
tasks sharing a cpu in the second node.  The patch would ensure that 4
tasks run in the first node and 2 in the second.

I ran some kernel compiles comparing this patch on a 2 node 4 cpu/2 cpu
system to show the benefits.  Without the patch I got 140 second elapsed
time.  With the patch I get 132 seconds (6% better).

Although it is not very common to have nodes with dissimilar cpu counts, it
is already happening.  PPC64 systems with partitioning have this happen,
and I expect it to be more common on ia32 as partitioning becomes more
common.

From: Chris Heath <chris@heathens.co.nz>

Here's a column counting bug that was lurking in a corner of n_tty.c.

From: Zwane Mwaikambo <zwane@linuxpower.ca>

smbfs tends to oops over a null server->ops->getattr in smb_proc_getattr().

Urban says:

 In 2.5 the server->ops is initialized when smbfs gets a connection, to
 match whatever the server is capable of or not. This happens after the
 mount syscall so smbfs is then mounted but not usable.

 Not sure if smb_lookup is always called before any other operation that
 uses server->ops. If it is then it would be enough to have a test there.

 Otherwise I will just change all users of server->ops to verify the
 pointer first and return -EIO or something.

Al Viro says (paraphrasing)

 ugh, we need mount2().

It doesn't look to me like we'll be getting mount2() in the 2.6 timeframe.
Zwane's patch implement's Urban's workaround.

From: Maneesh Soni <maneesh@in.ibm.com>

- hpfs_unlink() can race with lockless d_lookup(), as we can have situations
  where d_lookup() has successfully looked-up a dentry and at the sametime
  hpfs_unlink()--->d_drop() has dropped it. Taking the per dentry lock
  before checking the d_count in hpfs_unlink() solves this race condition.

From: Maneesh Soni <maneesh@in.ibm.com>

- nfs_unlink() can race with lockless d_lookup() as d_lookup() can
  successfully lookup a dentry for which nfs_unlink() can assume that no one
  else is using and can go ahead and do nfs_safe_remove() on it. By using
  per dentry lock, it is solved as we d_lookup() will fail the lookup for
  unhashed dentries.

From: Maneesh Soni <maneesh@in.ibm.com>

- d_invalidate() can incorrectly return success instead of returning -EBUSY
  as we can have situations where lockless d_lookup has found a dentry
  successfully before d_invalidate drops it

From: Ingo Molnar

Apparently our thread-creation performance has gone down the tubes again,
because the mm.free_area_cache search heuristic broke.

The initial, more naive hole-cache patch helped the testcode in the
beginning.  Then after some point glibc started creating a 'small hole' in
the vmas, which hole was _below_ the thread stacks, and which hole thus
prevented the intended operation of the cache.

The new code solves the problem by relaxing the 'smallest address hole cache'
rule a bit, the cache is now not re-set at every get_unmapped_area() time,
it's only re-set during unmaps.  It's also re-set if there are no allocatable
mappings at all - ie.  correctness is not affected.

From: David Mosberger <davidm@napali.hpl.hp.com>

Give the ia32 vsyscall DSO the same name as ia64's.

From: Stephen Smalley <sds@epoch.ncsc.mil>

This patch adds an AT_SECURE auxv entry to pass a boolean flag indicating
whether "secure mode" should be enabled (i.e.  sanitize the environment,
initial descriptors, etc) and allows each security module to specify the
flag value via a new hook.

New userland can then simply obey this flag when present rather than
applying other methods of deciding (sample patch for glibc-2.3.2 can be
found at http://www.cs.utah.edu/~sds/glibc-secureexec.patch).

This change enables security modules like SELinux to request secure mode
upon changes to other security attributes (e.g.  capabilities,
roles/domains, etc) in addition to uid/gid changes or even to completely
override the legacy logic.

The legacy decision algorithm is preserved in the default hook functions
for the dummy and capability security modules.

Credit for the idea of adding an AT_SECURE auxv entry goes to Roland
McGrath.