- 30 Sep, 2002 4 commits
-
-
http://jdike.stearns.org:5000/updates-2.5Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Ingo Molnar authored
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.
-
- 29 Sep, 2002 9 commits
-
-
Jeff Garzik authored
due to synchronize_irq() becoming a no-op when !CONFIG_SMP.
-
Jeff Dike authored
-
Jeff Dike authored
uml.ld.S.
-
David S. Miller authored
-
David S. Miller authored
-
David S. Miller authored
-
David S. Miller authored
-
David S. Miller authored
into nuts.ninka.net:/home/davem/src/BK/net-2.5
-
David S. Miller authored
into nuts.ninka.net:/home/davem/src/BK/net-2.5
-
- 30 Sep, 2002 1 commit
-
-
Arnaldo Carvalho de Melo authored
With this we avoid doing skb_clone on skbs that will not be kept on unacked lists.
-
- 29 Sep, 2002 26 commits
-
-
Arnaldo Carvalho de Melo authored
Thanks do Andries Brouwer for reporting the problem and suggesting a way to fix it.
-
Arnaldo Carvalho de Melo authored
Thanks to Andries Brouwer for providing a patch.
-
Arnaldo Carvalho de Melo authored
-
David S. Miller authored
-
David S. Miller authored
-
David S. Miller authored
-
David S. Miller authored
-
David Gibson authored
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.
-
David Brownell authored
Fix pci_pool_create() from calling device_create_file() under pools_lock. Found by the new "may_sleep" infrastructure.
-
Linus Torvalds authored
-
David S. Miller authored
into nuts.ninka.net:/home/davem/src/BK/net-2.5
-
http://gkernel.bkbits.net/net-drivers-2.5Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Jeff Garzik authored
into mandrakesoft.com:/home/jgarzik/repo/net-drivers-2.5
-
Jeff Garzik authored
into mandrakesoft.com:/home/jgarzik/repo/net-drivers-2.5
-
Jeff Garzik authored
(contributed by Francois Romieu)
-
Jeff Garzik authored
(contributed by James Blackwell)
-
Jeff Garzik authored
-
http://linux-isdn.bkbits.net/linux-2.5.isdnLinus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Kai Germaschewski authored
Keeping track of dialing / auto hangup is per ISDN channel, so should go into isdn_net_dev.
-
Kai Germaschewski authored
Again, ipppd has one kernel connection per channel in a MPPP setting, so we should keep track in isdn_net_dev.
-
Kai Germaschewski authored
Dialing happens per channel / isdn_net_dev, so the move the corresponding members there.
-
Kai Germaschewski authored
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.
-
David Mosberger authored
GCC currently warns when page-flags.h gets included before struct page is declared. Declare it.
-
Kai Germaschewski authored
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.
-
Kai Germaschewski authored
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.
-
Art Haas authored
-