This fixes a procfs crash noticed by Anton Blanchard.

The procfs code can have a reference even to an already exited task, so
it needs to follow special rules accessing p->sig.  The atomic-signals
patch made this bug happen at a much higher frequency, but procfs i
believe was buggy ever since, it potentially used the freed signal
structure - which just did not result in a crash like it does today.

The proper fix is to take the tasklist read-lock in
collect_sigign_sigcatch(), this excludes __exit_sighand() freeing the
signal structure prematurely.

due to synchronize_irq() becoming a no-op when !CONFIG_SMP.

Crud.  Looks like my patch making script was borken, so orinoco_pci.c
wasn't updated properly.  The patch below should fix that, and adds
some other minor updates (driver version 0.13a) as well.

Fix pci_pool_create() from calling device_create_file() under
pools_lock.

Found by the new "may_sleep" infrastructure.

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

into mandrakesoft.com:/home/jgarzik/repo/net-drivers-2.5

into mandrakesoft.com:/home/jgarzik/repo/net-drivers-2.5

(contributed by Francois Romieu)

(contributed by James Blackwell)

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

Keeping track of dialing / auto hangup is per ISDN channel, so should
go into isdn_net_dev.

Again, ipppd has one kernel connection per channel in a MPPP
setting, so we should keep track in isdn_net_dev.

Dialing happens per channel / isdn_net_dev, so the move the
corresponding members there.

This is the first step of a long series moving members between
isdn_net_local and isdn_net_dev.

Today, a one-to-one relationship between these both structures exist, so
it does not really matter where the members live. However, the goal
is to get a correspondence like

net_device -> isdn_net_local -> master isdn_net_device
                                           |
                                slave  isdn_net_device
                                           |
                                slave  isdn_net_device

where more than one isdn_net_device can exist per actual net_device,
due to channel bundling.

GCC currently warns when page-flags.h gets included before struct page
is declared. Declare it.

X25 needs notification if an interface is brought up or down, and
ethernet over ISDN creates a fake MAC address at open time, so put this
into appropriate callbacks as well.

The ->init() callback can be used for calling ether_setup() in case
of encapsulation "ISDN over ethernet", for the other cases it does not
make sense anyway.

i810-tco: Upgrade to version 0.05 .

Fix possible timer_alive race, add expect close support,
clean up ioctls (WDIOC_GETSTATUS, WDIOC_GETBOOTSTATUS and
WDIOC_SETOPTIONS), made i810tco_getdevice __init,
removed boot_status, removed tco_timer_read,
added support for 82801DB and 82801E chipset, general cleanup.

Add defines to pci_ids.h for 82801E and 82801DB I/O Controller Hub PCI-IDS.

Make i810_rng documentation the same as in 2.4.19

Fix free_irq() comment - it definitely is not callable
from interrupt context..

This removes the fat_search_long() in the vfat_add_entry().  This path
is already checked by the vfs layer whether file/directory exists.  So,
we don't need the fat_search_long() in vfat_add_entry().

The following is the result of created the 1000 files,

2.5.39
root@devron (a)[1007]# time ../../create

real    0m2.761s
user    0m0.006s
sys     0m2.752s
root@devron (a)[1008]#

2.5.39 + patch
root@devron (a)[1007]# time ../../create

real    0m1.601s
user    0m0.008s
sys     0m1.575s
root@devron (a)[1008]#

On FAT12, the current FAT driver recognizes 0xff8-0xfff as EOF, and it
writes in 0xff8 as EOF.  This is right behavior.  However, the firmware
of some MP3-Players recognize only 0xfff (standard EOF which Micorsoft
uses) as EOF.

So, we write 0xfff instead of 0xff8 as EOF, until the reason we need
values other than standard EOF is found.

[Randy Dunlap, I appreciate your help.]

X25 needs notification when encapsulation is set to X25 and when
it is changed to something else again, so let's have some callbacks
for init/cleanup.

Use a struct of methods and parameters to describe the
different kinds of network interfaces supported by isdn_net.c
and friends.