them do want to temporarily block signals.

Kernel users can also block signals that are normally unblockable
to user space, ie SIGKILL and SIGSTOP.

Make nfsd and autofs use the new interface, as an example to others. 

Do not crash on null pointer dereference, if cannot reread superblock.

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

  - a read_lock(&tasklist_lock) is missing around the group_send_sig_info()
    in send_sig_info().

 - session-IDs and group-IDs are set outside the tasklist lock. This
   causes breakage in the USB code. The correct fix is to do this:

I introduced the bug with the new pidhash.

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

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

into samba.org:/scratch/anton/sfr

into samba.org:/scratch/anton/sfr

  - moved inclusion of <linux/interrupt.h> from <sound/asound.h> to <sound/timer.h>
  - pmac driver - removed beep stuff for 2.5 kernels
  - USB driver - fixed compilation

We have 53c700.c and 53c7xx for the 7xx series and
ncr53c8xx for the 720.  The sym53c8xx_2 covers all the 8xx chips.

It's probably going to be a fifo, so it should be more efficient
for taking them off again

This should add synchronous support and Tagged Command Queueing.
At the moment, it cuts down on the number of command line options,
but we can add those back in later.

This patch also migrates the driver to the new device model for
both MCA and EISA.

The recent slab allocation changes mean that we no longer keep a
permanent list of commands on the device_queue list.  However,
certain pieces of SCSI code relied on being able to traverse this
list to find details of all outstanding commands (the error handler
being the prime example).  This code adds back a new dynamic cmd_list
which keeps the list of commands currently allocated to the device.
Since the list is dynamic, it is protected by a lock (list_lock).

into kernel.bkbits.net:/home/davem/net-2.5

If CONFIG_PREEMPT is enabled, and the kernel is preempted just before
do_debug() has a chance to save the debug register values, DR6 could be
read from the wrong CPU.

It is exactly the same problem as reading %cr2 in the page fault
handler.  Same fix: make the handler a interrupt gate, and enable
interrupts only once safe.

sys_exit_group() doesn't return any value, and obviously cannot.

So don't make the compiler unhappy about it by claiming it does.

Fix wrong order of process status. It's

	#define TASK_RUNNING            0
	#define TASK_INTERRUPTIBLE      1
	#define TASK_UNINTERRUPTIBLE    2
	#define TASK_STOPPED            4
	#define TASK_ZOMBIE             8
	#define TASK_DEAD               16

but SysRQ printout routines switch stopped and zombie around.

So, for one more time, here's another mailing of the same patch to fix
this brokenness.  In addition, fix the wrong comment in fs/proc/array.c

This fixes the signal code to not wake up threads with blocked signals,
especially noticeable with kernel threads that may not be able to handle
signals at all.

We also don't unnecessarily wake processes in TASK_UNINTERRUPTIBLE.

Sound drivers need <linus/interrupt.h> for tasklets

  - emu10k1 - fixed makefile to not build synth module when emu10k1 is not selected

  - cmipci driver cleanups (ac3 & surround)
  - replaced snd_dma_residue() with snd_dma_pointer()
  - GCC 3.3 warnings removal
  - timer interface
    - recoded using tasklet
    - improved slave timer locking (should be much faster)
    - added async support
  - improved ioctl32 wrapper functions
  - fixed Makefile problems (synth modules were build for not selected driver)
  - AC97 codec
    - improved SPSA control
    - moved reset function outside the main init code
    - improved ALC650 initialization
  - USB driver
    - added quirk for Roland XV-2020

For handle_stop_signal to do the special case for SIGKILL and have it
work right in all SMP cases (without changing all the existing ptrace
stops), it needs to at least set TIF_SIGPENDING on each thread before
resuming it.

handle_stop_signal addresses a related race for SIGCONT by setting
TIF_SIGPENDING already, so having SIGKILL handled the same way makes
sense.

Now it seems pretty clean to have handle_stop_signal resume threads for
SIGKILL, and have on SIGKILL special case in group_send_sig_info.

There is also an SMP race issue with cases like do_syscall_trace, i.e.
TASK_STOPPED state set without holding the siglock.  So I think
handle_stop_signal should call wake_up_process unconditionally.

Accomodate the signal locking moving from "tsk->sig" to "tsk->sighand".

into samba.org:/scratch/anton/sfr

This is required to get make the old LinuxThread semantics work
together with the fixed-for-POSIX full signal sharing. A traditional
CLONE_SIGHAND thread (LinuxThread) will not see any other shared
signal state, while a new-style CLONE_THREAD thread will share all
of it.

This way the two methods don't confuse each other.

already take care of it.

This fixes kernel threads that _do_ block SIGKILL/STOP.

into samba.org:/scratch/anton/sfr

Spotted by davem.  Strange that it ever worked.  Don't know why the compiler
didn't warn...

This changes do_sigaction to avoid read_lock(&tasklist_lock) on every
call.  Only in the fairly uncommon cases where it's really needed will
it take that lock (which requires unlocking and relocking the siglock
for locking order).

I also changed the ERESTARTSYS added in my earlier patch to ERESTARTNOINTR.
That is an "instantaneous" case, and there is no reason to have it possibly
return EINTR if !SA_RESTART (which AFAIK sigaction never could before, and
it might not be kosher by POSIX); rollback is always better.

This patch removes all the comments on the SA_NOCLDWAIT definitions,
since SA_NOCLDWAIT is fully supported now.

This fixes the following common misspellings and their variants.

  consistant -> consistent
  dependant  -> dependent
  persistant -> persistent

into samba.org:/scratch/anton/sfr