- 15 Mar, 2005 4 commits
-
-
Herbert Xu authored
This patch replaces most of the other uses of dst_pmtu with dst_mtu. As far as I can tell these are either identical because dst->path == dst, or they're a straightforward replacement of (the slightly incorrect) dst_pmtu(dst) - dst->header_Len with dst_mtu(dst). Signed-off-by:
Herbert Xu <herbert@gondor.apana.org.au> Signed-off-by:
David S. Miller <davem@davemloft.net>
-
Herbert Xu authored
This patch uses dst_mtu instead of dst_pmtu in the various tunnel implementations. As it is they simply ignore the IPsec overhead. This leads to bogus MTU values inside the tunnels. Signed-off-by:
-
Herbert Xu authored
This patch fixes the IPsec overhead handling in ip_append_data and ip6_append_data. As it is they assume that the IPsec overhead is constant. This is not true as with ESP the IPsec overhead will vary as the MTU varies. The result is that they may produce packets that will exceed the MTU when ESP is used. Had it taken the trailer_len into account, it would have produced packets less than the real MTU. By switching to dst_mtu we get the optimal result. Signed-off-by:
-
Andrew Morton authored
Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
-
- 14 Mar, 2005 20 commits
-
-
bk://kernel.bkbits.net/davem/sparc-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
bk://kernel.bkbits.net/davem/net-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Robert Olsson authored
The current code bombs out with preemption enabled. Signed-off-by: -
Herbert Xu authored
Signed-off-by:
-
Stephen Hemminger authored
Some users, set hold time to zero on bridge so it always does flooding. This is usually when using it with wireless. The new RCU based code changed the behaviour so the bridge would not flood for one GC interval. This patch restores the original behaviour. Signed-off-by: -
Herbert Xu authored
This can elicit ICMP message output and thus result in a deadlock. Signed-off-by:
-
Andre Tomt authored
Signed-off-by:
Andre Tomt <andre@tomt.net> Signed-off-by:
-
Harald Welte authored
Signed-off-by:
Harald Welte <laforge@netfilter.org> Signed-off-by:
-
Ralf Bächle authored
In an attempt to return a locked socket ax25_get_socket() was calling lock_sock() with a spinlock held, bad idea. Making matters worse it's only user is running in bottom half context resulting in a potencial attempt to sleep in bottom half context, so fix the locking there as well. Signed-off-by: -
Herbert Xu authored
netlink_autobind has always set nlk_sk(sk)->groups to zero. This is unnecessary because sk_alloc already zeroes the entire structure. Since a socket can only be bound once netlink_autobind doesn't need to zero groups at all. This had been safe until I added mc_list. Now it is possible for netlink_bind to race against netlink_autobind running on the same socket on another CPU. The result would be a socket that's on mc_list with groups set to zero. This socket will be left on the list even after it is destroyed. The fix is to remove the zeroing in netlink_autobind. Signed-off-by:
-
Herbert Xu authored
While replacing dst_pmtu in ip6_output I found this little gem. In ip6_forward we're not reloading the dst pointer after calling xfrm6_route_forward. So all subsequent dereferences of dst will refer to its pre-IPsec value. The solution is of course to refresh its value. Signed-off-by:
-
Herbert Xu authored
I'm now cleaning up all users of dst_pmtu with the aim of replacing dst_pmtu with dst_mtu. I'm going to start with the ones that actually fix bugs. This patch fixes the length calculation in icmp_send. As it is we're overestimating the space available by including the space that would be used up by IPsec encapsulation. IPv6 doesn't have this problem since its calculation is based on 1280 instead of the PMTU. Signed-off-by:
-
Herbert Xu authored
When cleaning up the remaining users of dst_pmtu I noticed that local_df wasn't being treated correctly in IPsec. In fact, if you socket's dst went over IPsec, local_df is essentailly ignored. This patch fixes that. Signed-off-by:
-
Bart De Schuymer authored
The patch below fixes an smp race that happens on such systems under heavy load. This bug was reported and solved by Steve Herrell <steve_herrell@yahoo.ca> Signed-off-by:
Bart De Schuymer <bdschuym@pandora.be> Signed-off-by:
-
Thomas Graf authored
Use dev_get_flags() in inet6_fill_ifinfo() to fetch interface flags to ensure correctly reporting IFF_PROMISC and IFF_ALLMULTI flags. Signed-off-by:
Thomas Graf <tgraf@suug.ch> Signed-off-by:
-
David S. Miller authored
Otherwise ia64 and sparc64 explode with the new ptwalk iterators. The pgd level stuff does not handle virtual address space holes (sparc64) and region based PGD indexing (ia64) properly. It only matters in functions like clear_page_range() which potentially walk over more than a single VMA worth of address space. Signed-off-by: -
David S. Miller authored
into sunset.davemloft.net:/home/davem/src/BK/sparc-2.6
-
David S. Miller authored
Signed-off-by: -
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
- 13 Mar, 2005 16 commits
-
-
Adrian Bunk authored
This patch removes three unused variables. Pavel Machek and H. Peter Anvin have already confirmed it's correct. Signed-off-by:
Adrian Bunk <bunk@stusta.de> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Adrian Bunk authored
I haven't found any modular usage of kmap_{pte,port} on !ppc in the kernel. Signed-off-by: -
Adrian Bunk authored
flush_tlb_all was exported on i386 for a DRM usage - that was removed in 2003. I haven't found any modular usage of *flush_tlb_all in the kernel. Signed-off-by:
-
Domen Puncer authored
convert from pci_module_init to pci_register_driver Signed-off-by:
Christophe Lucas <c.lucas@ifrance.com> Signed-off-by:
Domen Puncer <domen@coderock.org> Acked-by:
Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by:
-
Domen Puncer authored
Use msleep_interruptible() instead of schedule_timeout() to guarantee the task delays as expected. Also remove macro MS_TO_HZ() and replace with msecs_to_jiffies(). Signed-off-by:
Nishanth Aravamudan <nacc@us.ibm.com> Signed-off-by:
-
Yoichi Yuasa authored
This patch fixes section type conflict about mpc30x CC arch/mips/pci/fixup-mpc30x.o arch/mips/pci/fixup-mpc30x.c:26: error: internal_func_irqs causes a section type conflict make[1]: *** [arch/mips/pci/fixup-mpc30x.o] Error 1 make: *** [arch/mips/pci] Error 2 Signed-off-by:
Yoichi Yuasa <yuasa@hh.iij4u.or.jp> Signed-off-by:
-
Domen Puncer authored
Make code more readable with list_for_each_reverse. Signed-off-by:
Maximilian Attems <janitor@sternwelten.at> Acked-by:
Jeff Dike <jdike@addtoit.com> Signed-off-by:
-
Domen Puncer authored
Use wait_event_interruptible() instead of the deprecated interruptible_sleep_on(). The replacements were all straight-forward as every sleep was conditionally-looped. Patch is compile-tested (still warns about {save,restore}_flags(),cli()). Signed-off-by: -
Domen Puncer authored
Replace deprecated interruptible_sleep_on_timeout() function calls with direct wait-queue usage. There may be an existing problem with this driver, as I am not finding any wake_up_interruptible() callers for the waitq. Patch is compile-tested. Signed-off-by:
-
Domen Puncer authored
convert from pci_module_init to pci_register_driver Signed-off-by:
-
Domen Puncer authored
convert from pci_module_init to pci_register_driver Signed-off-by:
-
Domen Puncer authored
Use ssleep() instead of schedule_timeout() to guarantee the task delays as expected. The original code does use TASK_INTERRUPTIBLE, but does not check for signals or early return from schedule_timeout() so ssleep() seems more appropriate. Signed-off-by:
-
Domen Puncer authored
convert from pci_module_init to pci_register_driver Signed-off-by:
-
Domen Puncer authored
Remove nowhere referenced file. (egrep "filename\." didn't find anything) Signed-off-by:
-
Domen Puncer authored
Use msleep_interruptible() instead of schedule_timeout() to guarantee the task delays as expected. Signed-off-by:
-
Domen Puncer authored
Inserts a set_current_state(TASK_INTERRUPTIBLE) before the schedule_timeout() call. Without this change, after the first iteration of the loop, schedule_timeout() will not only return immediately, but the loop will break, as the conditional will no longer be satisfied. In fact, this conditional makes little sense given the workings of schedule_timeout. The timeout variable is ignored, as well, and I'm fairly certain that it should be included in the loop conditional. That way, if the timeout expires before a signal hits, -ETIME will be returned by fdc_interrupt_wait() instead of -EINTR. Signed-off-by:
-
