and print a msg if used

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

When a raid1 or raid5 array is in 'safe-mode', then the array
is marked clean whenever there are no outstanding write requests,
and is marked dirty again before allowing any write request to
proceed.

This means than an unclean shutdown while no write activity is happening
will NOT cause a resync to be required.  However it does mean extra
updates to the superblock.

Currently safe-mode is turned on by sending SIGKILL to the raid thread
as would happen at a normal shutdown.  This should mean that the
reboot notifier is no longer needed.

After looking more at performance issues I may make safemode be on
all the time.  I will almost certainly make it on when RAID5 is degraded
as an unclean shutdown of a degraded RAID5 means data loss.

This code was provided by  Angus Sawyer <angus.sawyer@dsl.pipex.com>

This allows the thread to easily identified and signalled.
The point of signalling will appear in the next patch.

From Art Haas <ahaas@airmail.net>:

This converts md.c to use C99 initializers to improve readability and
remove warnings if '-W' is used.

by the nature of multipath, already be in-sync, so we should set the
in-sync flag.

From Andrew Morton <akpm@digeo.com>:

gcc-2.95.3 is getting an internal compiler error with CONFIG_LBD=y.  Reorganising
the code a bit made it go away.

This call the super_90_load is meant to make sure that the new
superblock is consistant with a pre-exisitnig one (on rdev0)...  but
rdev0 was not passed :-(

From Art Haas <ahaas@airmail.net>:

This converts the file to use C99 named initializers.  These change make
the file compile with fewer warnings if '-W' is added to the compile
flags, and may enhance code readability.  Let me know if you think this
should be sent to Linus.

From Trond:

  When the nanosecond resolution on [acm]time was introduced to 2.5.x,
the knfsd GETATTR responses were converted to make use of the
nanosecond field, but the pre/post WCC attributes were not. This will
lead to a lot of unnecessary cache invalidations on the clients.

The following trivial patch should fix up knfsd so that it stores and
encodes the full 'struct timespec' in both pre and post attribute
fields.

Problem was that the cache was being updated inplace, rather
than swapping in a new entry, so old filesystem pointers
were overwritten without being released.

As nfsv4 does some reply encoding while processing
requests, the code which tries to put the overall status
at the head of the reply fails.

With this patch, we take the address for the overall
status very early so NFSv4's encoding wont confuse us.

NFS replies can have a 'tail' after a 'data' component
(for read, readlink, readdir).

For nfsv2 and v3 this tail is in the same page as the head.
For nfsv4, this tail is in a separate page.

We need to keep track of which page so that it right one
gets sent.  This patch does that.

From Ted Phelps <phelps@dstc.edu.au>

The NFSv3 readdirplus path doesn't check to see if maxcount is less
than the size of a page before it fills it up, possibly overwriting
random bits of memory.  At least, it makes my Solaris NFSv3 client
work.

The attached patch, against 2.5.58, adds this check in a way which is
consistent with the way readdir does under both NFSv2 andNFSv3.

into raven.il.steeleye.com:/home/jejb/BK/scsi-for-linus-2.5

This is a compile fix for bug:
http://bugme.osdl.org/show_bug.cgi?id=360

This patch is against scsi-misc-2.5.

Testing: Compile only

-andmike
--
Michael Anderson
andmike@us.ibm.com

 aha152x_stub.c |    2 +-
 nsp_cs.c       |   40 ++++++++++++++++++++--------------------
 nsp_message.c  |    2 +-
 3 files changed, 22 insertions(+), 22 deletions(-)

When compiling random.c without SYSCTL defined a warning is
issued about free_entropy_store being defined but not used.
Put ifdef's around the functions.

I could have moved the whole function, but it logically belongs
to this part of the file.

When compiling without PROC_FS enabled a warning is issued about
proc_dma_show defined but not used.

Move both versions of proc_dma_show inside the #ifdef CONFIG_PROC_FS

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

into tp1.ruhr-uni-bochum.de:/scratch/kai/kernel/v2.5/linux-2.5.make

The 3 lines being deleted are repeated from above (in same file).
I pulled the 2 lines being added from an earlier version of the patch.

This is an update to the EISA/sysfs code :

 - Separate bus root code from generic code.
 - Add driver for PCI/EISA bridge.
 - Hacked parisc eisa driver so it can act as a root device.
 - Add driver for so-called virtual root (for bridge-less systems).
 - Allow multiple roots.
 - Moved quirk_eisa_bridge from alpha to generic code, since
   the EISA code needs it now (on x86, for example...).
 - 3c59x :
   Prevent driver from returning ENODEV in case it has registered with
   the EISA framework, but no device has been found yet (it happends
   when the driver is built into the kernel, and the EISA bus root has
   not been discovered yet).

It's been discussed on lkml, and all suggestions (mainly from Ivan
Kokshaysky <ink@jurassic.park.msu.ru>) have been taken into account.

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

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

jfs_sync_fs was implemented using the same code as the unmount code to flush
the journal and wait for the journal to quiesce.  Since jfs_sync_fs may  be
called while the volume is under heavy use, we can end up waiting
indefinately.  Code in jfs_flush_journal meant to detect a hang at unmount
time may be triggered in this case causing a trap.  This patch changes
jfs_sync_fs to only wait until the most recent transaction has been
commited to disk, rather than waiting until the commit queue is empty.

state changes due to execve() and exit(). We need to hold the tasklist
lock to guarantee stability of "task->sighand".

Update the ARM signal handling to use the generic
get_signal_to_deliver() implementation.  There is a caveat though -
ARM has no hardware support for single stepping, and thus needs the
kernel to help provide this.

We introduce a new ptrace flag for this, PT_SINGLESTEP, which
indicates to architecture specific code that it should take extra
actions in the signal handler to set and/or clear breakpoints as
appropriate.

From Geoffrey Lee <glee@gnupilgrims.org>.