14 Jun, 2005
17 commits
-
This adds a clause that notes explicitly that the person doing the
sign-off knows that the project (and his sign-off) is public and will
possibly get archived and re-distributed. -
This patch alows you to change the source address of icmp error
messages. It applies cleanly to 2.6.11.11 and retains the default
behaviour.In the old (default) behaviour icmp error messages are sent with the ip
of the exiting interface.The new behaviour (when the sysctl variable is toggled on), it will send
the message with the ip of the interface that received the packet that
caused the icmp error. This is the behaviour network administrators will
expect from a router. It makes debugging complicated network layouts
much easier. Also, all 'vendor routers' I know of have the later
behaviour.Signed-off-by: David S. Miller
-
link local address.
Signed-off-by: Sridhar Samudrala
Signed-off-by: David S. Miller -
Signed-off-by: Neil Horman
Signed-off-by: Sridhar Samudrala
Signed-off-by: David S. Miller -
Signed-off-by: Vladislav Yasevich
Signed-off-by: Sridhar Samudrala
Signed-off-by: David S. Miller -
Signed-off-by: Neil Horman
Signed-off-by: Sridhar Samudrala -
Signed-off-by: Vladislav Yasevich
Signed-off-by: Sridhar Samudrala
Signed-off-by: David S. Miller -
Userland layer-2 tunneling devices allocated through the TUNTAP driver
(drivers/net/tun.c) have a type of ARPHRD_NONE, and have no link-layer
address. The kernel complains at regular interval when IPv6 Privacy
extension are enabled because it can't find an hardware address :Dec 29 11:02:04 auguste kernel: __ipv6_regen_rndid(idev=cb3e0c00):
cannot get EUI64 identifier; use random bytes.IPv6 Privacy extensions should probably be disabled on that sort of
device. They won't work anyway. If userland wants a more usual
Ethernet-ish interface with usual IPv6 autoconfiguration, it will use a
TAP device with an emulated link-layer and a random hardware address
rather than a TUN device.As far as I could fine, TUN virtual device from TUNTAP is the very only
sort of device using ARPHRD_NONE as kernel device type.Signed-off-by: Rémi Denis-Courmont
Acked-by: YOSHIFUJI Hideaki
Signed-off-by: David S. Miller -
We saw following trace several times:
|BUG: using smp_processor_id() in preemptible [00000001] code: httpd/30137
|caller is icmpv6_send+0x23/0x540
| [] smp_processor_id+0x9b/0xb8
| [] icmpv6_send+0x23/0x540This is because of icmpv6_socket, which is the only one user of
smp_processor_id() in icmpv6_send(), AFAIK.Since it should be used in non-preemptive context,
let's defer the dereference after disabling preemption
(by icmpv6_xmit_lock()).Signed-off-by: YOSHIFUJI Hideaki
Signed-off-by: David S. Miller -
Patch from Nicolas Pitre
Signed-off-by: Nicolas Pitre
Signed-off-by: Russell King -
From: Ralf Baechle
There are archives of the old list at http://oss.sgi.com/archives/netdev
Signed-off-by: Andrew Morton
Signed-off-by: David S. Miller -
Signed-off-by: Randy Dunlap
Signed-off-by: David S. Miller -
Signed-off-by: Andi Kleen
Signed-off-by: David S. Miller -
uses __be16, but does not directly include
. Add this in, so that dhcp/net-tools token ring code
can compile again.Signed-off-by: Tom Rini
Signed-off-by: David S. Miller -
This fixes a data corruption error for mail delivery applications that
expect to be able to do posix locking and then append writes on NFS.Signed-off-by: Trond Myklebust
Signed-off-by: Linus Torvalds
13 Jun, 2005
8 commits
-
This makes the EHCI driver spin a bit longer before concluding that the
port reset failed. "Obviously safe."It allows some devices to enumerate that previously didn't. We've seen
a bunch of these problem reports recently, this will make some go away.As reported by Michael Zapf , some EHCI
controllers seem to take forever to finish port resets and produce
"port N reset error -110" type errors. Spinning a bit longer helps.Signed-off-by: David Brownell
Signed-off-by: Linus Torvalds -
The pwc chainsaw session left some setups not working. There is a
sanity check on compression buffers that simply isn't right any more as
we never allocate one.This doesn't address the email and other changes. I'll do those
tomorrow if I get time, but it is the minimal fix for the code and basic
feature set.Signed-off-by: Alan Cox
Signed-off-by: Linus Torvalds -
The current radeonfb memset's the framebuffer to 0 when loaded. This
removes occasional artifacts but has the nasty side effect that if you
load radeonfb without framebuffer console, you destroy the VGA text
buffer, font, etc... radeon must not touch the framebuffer content when
it doesn't "own" it.Signed-off-by: Benjamin Herrenschmidt
Signed-off-by: Linus Torvalds -
M68k: Mark Sun-3 NCR5380 SCSI broken until NCR5380_abort() and
NCR5380_bus_reset() are replaced with real new-style EH routines (the old EH
SCSI constants were removed in 2.6.12-rc3).Signed-off-by: Geert Uytterhoeven
Signed-off-by: Linus Torvalds -
Signed-off-by: Geert Uytterhoeven
Signed-off-by: Linus Torvalds -
Now m68k no longer sets HAVE_ARCH_GET_SIGNAL_TO_DELIVER, can it be removed
completely? Or may ARM26 still need it? Note that its usage was removed from
kernel/signal.c about 2 months ago.Signed-off-by: Geert Uytterhoeven
Signed-off-by: Linus Torvalds -
Signed-off-by: Geert Uytterhoeven
Signed-off-by: Linus Torvalds -
Patch from David Brownell
The ARM generic Kconfig filters out IDE options ... except for
an error prone ARMload of special cases.
This adds one general case to the systems that will offer IDE options:
kernels with PCMCIA support, which probably want to use IDE to access
CompactFlash cards. This might allow many (most?) of the other cases
to disappear, for systems that only see IDE hardware through CF cards.
Right now this one patch is used to gate access to CF cards, including
MicroDrives, for both omap_cf and at91_cf drivers.Signed-off-by: David Brownell
Signed-off-by: Russell King
11 Jun, 2005
3 commits
-
The patch to add them keeps on getting applied, over and
over again ;)Hopefully no more.
10 Jun, 2005
12 commits
-
This removes a bogus hack from the radeon IRQ handler.
There is a better fix from myself and benh in DRM CVS but I'll wait
until 2.6.13-rc so it gets more testing.Signed-off-by: Dave Airlie
-
Add pci identifier for i945G chipset
Signed-off-by: Dave Airlie
-
Despite all the care lately in making the powermac sleep/wakeup as
robust as possible, there is still a nasty related to the use of cpufreq
on PMU based machines. Unfortunately, it affects paulus old powerbook
so I have to fix it :)We didn't manage to understand what is precisely going on, it leads to
memory corruption and might have to do with RAM not beeing properly
refreshed when a cpufreq transition is done right before the sleep.The best workaround (and less intrusive at this point) we could come up
with is included in this patch. We basically do _not_ force a switch to
high speed on suspend anymore (that is what is causing the problem) on
those machines. We still force a speed switch on wakeup (since we don't
know what speed we are coming back from sleep at, and that seems to work
fine).Since, during this short interval, the actual CPU speed might be
incorrect, we also hack around by multiplying loops_per_jiffy by 2 (max
speed factor on those machines) during early wakeup stage to make sure
udelay's during that time aren't too short.For after 2.6.12, we'll change udelay implementation to use the CPU
timebase (which is always constant) instead like we do on ppc64 and thus
get rid of all those problems.Signed-off-by: Benjamin Herrenschmidt
Signed-off-by: Linus Torvalds -
My patch from a few weeks back (now in mainline), called "Cleanup skbs to
prevent unregister_netdevice() hanging", can cause our TX timeout code to
fire on machines with lots of VLANs (because it takes > 2 seconds between
when we stop the queues and when we're finished stopping the connections).When that happens the TX timeout code freaks out and does a WARN_ON()
because as far as it's concerned there shouldn't be a TX timeout happening,
which is fair enough.I have a "proper" fix for this, which is to a) do refcounting on
connections and b) implement a proper ack timer so we don't keep unacked
skbs lying around for ever. But for 2.6.12 I propose just supressing the
WARN_ON(). Users will still see the "NETDEV WATCHDOG" warning, but that's
not nearly as bad as a WARN_ON() which users interpret as an Oops.Signed-off-by: Michael Ellerman
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Add a definition for PPC 405EP which was lost somehow during 2.4 -> 2.6
transition.Recent change to arch/ppc/kernel/misc.S ("Fix incorrect CPU_FTR fixup usage
for unified caches") triggered this bug and 405EP boards don't boot
anymore.Signed-off-by: Eugene Surovegin
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
MSI functionality is broken on the GC_LE x86 chipset that Serverworks
developed and that is being used in various platforms today. Broadcom is
going to push out to the kernel MSI enabled Gigabit drivers (in the very
near future), and we would like to make sure that MSI does not get
enabled on any platforms using the GC_LE chipset (device id 0x17).
Following the AMD 8131 example, I am including a patch to disable MSI
functionality when a GCNB_LE is detected. Please let me know if there
are any issues with this. This is a permanent fix for this chipset, as
the hardware will not be updated.Signed-off-by: Narendra Sankar
Signed-off-by: Greg Kroah-Hartman -
and add_to_page_cache fails.
Thanks to Shaggy for pointing out the fix.
Signed-off-by: Steve French (sfrench@us.ibm.com)
Signed-off-by: Shaggy (shaggy@us.ibm.com) -
Patch from Vincent Sanders
This fixes the "multiple definitions of cpufreq_get" build faliure on
the hackkit SA1100 platform.Signed-off-by: Vincent Sanders
Signed-off-by: Russell King
