into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

OK, here's ->d_parent stuff unrelated to printk.  Looking into printk
right now...

Protect d_parent with "dparent_lock", making ready to get rid of
BKL for d_move().

[Alan: also applies to 2.2.x]

William Stearns: linux/fs/file.c comment fix

	Patch below does the following:

*	removes dead code from wanproc.c.   When file looks like
#ifdef LINUX_2_4
<800 lines>
#else
<900 lines>
#endif
	there's no excuse for keeping all that junk around.
*	switches wanproc.c to use of seq_file
*	removes dead code from wanmain.c (again, dead == never seen by cc1).
*	fixes indentation in both
*	removes buttloads of trailing spaces in these files, while we are
	at it.

See if it's OK with you...

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

into vaio.(none):/home/kai/kernel/linux-2.5.isdn

into vaio.(none):/home/kai/kernel/linux-2.5.isdn

Preparation to adding new method:
 new helper - shutdown_super().  It is cut from kill_super() and
 it had absorbed all actions done with superblock contents -
 now kill_super(s) is simply

	struct file_system_type *fs = s->s_type;
	if (!deactivate_super(s))
		return;
		shutdown_super(s);
	put_filesystem(fs);

 and shutdown_super() is going to become a method.

Now remove_super() is called only from kill_super().  We move
the code that closes device/drops reference to filesystem type
from remove_super() into its caller.

* missing yield() added to grab_super() (on failure exit).  Without
  that we have a nasty race - if get_sb_bdev() happens just before
  we grab ->s_umount in kill_super(), we are going to have
  get_sb_bdev() spinning indefinitely long without yielding CPU,
  so that kill_super() could make progress (and break the loop).

* in kill_super() code that does actual superblock shutdown is
  wrapped in if (sb->s_root) {}.  That condition is true for
  all old callers of kill_super(), so we don't change existing
  behaviour.

* instances of deactivate_super()/remove_super() (after failed
  call of foo_fill_super()) are replaced with
	up_write(&s->s_umount);
	kill_super(s);
  - now it becomes legitimate (kill_super() works on such guys and
  does exactly what we want).

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

here's much simpler fix (both 2.4 and 2.5):

- cleanup patch from Hugh Dickins, fix up drivers to use vmalloc_to_page() instead of local hacks of uvirt_to_kva(). (and related fixes.)

- new, less intrusive and faster migration method:

/*
 * This is how migration works:
 *
 * 1) we queue a migration_req_t structure in the source CPU's
 *    runqueue and wake up that CPU's migration thread.
 * 2) we down() the locked semaphore => thread blocks.
 * 3) migration thread wakes up (implicitly it forces the migrated
 *    thread off the CPU)
 * 4) it gets the migration request and checks whether the migrated
 *    task is still in the wrong runqueue.
 * 5) if it's in the wrong runqueue then the migration thread removes
 *    it and puts it into the right queue.
 * 6) migration thread up()s the semaphore.
 * 7) we wake up and the migration is done.
 */

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

-
 make vma->vm_next_share and vma->vm_pprev_share
  a proper list.h list as well.

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

the lvm-patch that went into 2.5.5 missed the changes in lvm.h and is
still not compileable. This patch adds those changes. The kernel i'm
running right now has this patch and /var and /home on lvm.

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

A forward-port of all the .text.exit fixes which went into
2.4.   Also contains a couple of s/MINOR/minor/ changes.

Al updated Documentation/filesystems/porting with 2.5 changes but there
is no mention of lseek.  The following patch, against 2.5.5, adds lseek
to the list of functions that no longer are called with the BKL.

	Robert Love

The attached patch implements proper locking in ALSA lseek methods.
Note ALSA has 3 lseek implementations, but only:

	sound/core/info.c :: snd_info_entry_llseek()

requires locking.  I wrapped the function in the BKL.  According to
Jaroslav Kysela the gus_mem_proc method is only called from above.  The
third lseek, in hwdep.c, clearly doesn't need locking.  Without this
patch, the above lseek is not safe.

	Robert Love

This patch add the validity check of 2 values (fats, reserved). These
values must not be 0.

OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

Here enclosed patch for eata.c, eata.h, u14-34f.c, u14-34f.h
to be applied to lk-2.5.5.

eata.c:
       + Remove any reference to virt_to_bus().
       + Fix pio hang while detecting multiple HBAs.
       + Fixed a board detection bug: in a system with
         multiple ISA/EISA boards, all but the first one
          were erroneously detected as PCI.

u14-34f.c:
       + Remove any reference to virt_to_bus().
       + Fix pio hang while detecting multiple HBAs.

After BKL was moved from the VFS into the filesystem's methods in the lookup
call, we do not need to check BKL is actually held (we know it is not).
This patch patch removes unneeded lock_depth check.
Without this patch reiserfs cannot be used on SMP.

2.5.5 Oopses at boot time with a disk in a zipdrive.
With this patch all is fine. I have not read the
patch, certainly not checked it for correctness,
just observed that it works for me.
I think the author is Rich Baum.

Andries

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

use spin_[un]lock_irq{save,restore}, instead of defining static
inline functions to do the same thing (but possibly in a non-portable
way).

and wavelan_cs to new wireless API.

into flint.arm.linux.org.uk:/usr/src/linux-bk-2.5/linux-2.5-rmk

data.

its modes of operation.