linux-toradex.git/include/linux, branch v2.6.31.7

net: fix sk_forward_alloc corruption

2009-12-08T18:22:01+00:00

[ Upstream commit: 9d410c796067686b1e032d54ce475b7055537138 ]

On UDP sockets, we must call skb_free_datagram() with socket locked,
or risk sk_forward_alloc corruption. This requirement is not respected
in SUNRPC.

Add a convenient helper, skb_free_datagram_locked() and use it in SUNRPC

Reported-by: Francis Moreau 
Signed-off-by: Eric Dumazet 
Signed-off-by: David S. Miller 
Signed-off-by: Greg Kroah-Hartman

powerpc: Fix some late PowerMac G5 with PCIe ATI graphics

2009-11-10T00:23:15+00:00

commit cede3930f0ca6fef353fa01306c72a01420bd45e upstream.

A misconfiguration by the firmware of the U4 PCIe bridge on PowerMac G5
with the U4 bridge (latest generations, may also affect the iMac G5
"iSight") is causing us to re-assign the PCI BARs of the video card,
which can get it out of sync with the firmware, thus breaking offb.

This works around it by fixing up the bridge configuration properly
at boot time. It also fixes a bug where the firmware provides us with
an incorrect set of accessible regions in the device-tree.

Signed-off-by: Benjamin Herrenschmidt 
Signed-off-by: Greg Kroah-Hartman

param: fix lots of bugs with writing charp params from sysfs, by leaking mem.

2009-11-10T00:22:17+00:00

commit 65afac7d80ab3bc9f81e75eafb71eeb92a3ebdef upstream.

e180a6b7759a "param: fix charp parameters set via sysfs" fixed the case
where charp parameters written via sysfs were freed, leaving drivers
accessing random memory.

Unfortunately, storing a flag in the kparam struct was a bad idea: it's
rodata so setting it causes an oops on some archs.  But that's not all:

1) module_param_array() on charp doesn't work reliably, since we use an
   uninitialized temporary struct kernel_param.
2) there's a fundamental race if a module uses this parameter and then
   it's changed: they will still access the old, freed, memory.

The simplest fix (ie. for 2.6.32) is to never free the memory.  This
prevents all these problems, at cost of a memory leak.  In practice, there
are only 18 places where a charp is writable via sysfs, and all are
root-only writable.

Reported-by: Takashi Iwai 
Cc: Sitsofe Wheeler 
Cc: Frederic Weisbecker 
Cc: Christof Schmitt 
Signed-off-by: Rusty Russell 
Signed-off-by: Greg Kroah-Hartman

8250_pci: add IBM Saturn serial card

2009-11-10T00:22:13+00:00

commit c68d2b1594548cda7f6dbac6a4d9d30a9b01558c upstream.

The IBM Saturn serial card has only one port. Without that fixup,
the kernel thinks it has two, which confuses userland setup and
admin tools as well.

[akpm@linux-foundation.org: fix pci-ids.h layout]
Signed-off-by: Benjamin Herrenschmidt 
Acked-by: Alan Cox 
Cc: Michael Reed 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds 
Acked-by: Alan Cox 
Signed-off-by: Greg Kroah-Hartman

connector: Removed the destruct_data callback since it is always kfree_skb()

2009-10-22T22:11:55+00:00

(cherry picked from commit f4b5129f5e838942f759c2637967441cf4a98c20)

Signed-off-by: Philipp Reisner 
Acked-by: Lars Ellenberg 
Acked-by: Evgeniy Polyakov 
Signed-off-by: David S. Miller 
Signed-off-by: Greg Kroah-Hartman

connector: Provide the sender's credentials to the callback

2009-10-22T22:11:55+00:00

commit 7069331dbe7155f23966f5944109f909fea0c7e4 upstream

Signed-off-by: Philipp Reisner 
Signed-off-by: Lars Ellenberg 
Acked-by: Evgeniy Polyakov 
Signed-off-by: David S. Miller 
Signed-off-by: Greg Kroah-Hartman

connector: Keep the skb in cn_callback_data

2009-10-22T22:11:54+00:00

(cherry picked from commit 5491c43845dae6c68cb4edbcf2e2dde9a32a863d)

Signed-off-by: Philipp Reisner 
Signed-off-by: Lars Ellenberg 
Acked-by: Evgeniy Polyakov 
Signed-off-by: David S. Miller 
Signed-off-by: Greg Kroah-Hartman

USB: serial: don't call release without attach

2009-10-22T22:11:49+00:00

commit a4720c650b68a5fe7faed2edeb0ad12645f7ae63 upstream.

This patch (as1295) fixes a recently-added bug in the USB serial core.
If certain kinds of errors occur during probing, the core may call a
serial driver's release method without previously calling the attach
method.  This causes some drivers (io_ti in particular) to perform an
invalid memory access.

The patch adds a new flag to keep track of whether or not attach has
been called.

Signed-off-by: Alan Stern 
Tested-by: Jean-Denis Girard 
Signed-off-by: Greg Kroah-Hartman

smsc95xx: fix transmission where ZLP is expected

2009-10-12T19:40:28+00:00

[ Upstream commit ec4756238239f1a331d9fb95bad8b281dad56855 ]

Usbnet framework assumes USB hardware doesn't handle zero length
packets, but SMSC LAN95xx requires these to be sent for correct
operation.

This patch fixes an easily reproducible tx lockup when sending a frame
that results in exactly 512 bytes in a USB transmission (e.g. a UDP
frame with 458 data bytes, due to IP headers and our USB headers).  It
adds an extra flag to usbnet for the hardware driver to indicate that
it can handle and requires the zero length packets.

This patch should not affect other usbnet users, please also consider
for -stable.

Signed-off-by: Steve Glendinning 
Signed-off-by: David S. Miller 
Signed-off-by: Greg Kroah-Hartman

tracing: correct module boundaries for ftrace_release

2009-10-12T19:40:09+00:00

commit e7247a15ff3bbdab0a8b402dffa1171e5c05a8e0 upstream.

When the module is about the unload we release its call records.
The ftrace_release function was given wrong values representing
the module core boundaries, thus not releasing its call records.

Plus making ftrace_release function module specific.

Signed-off-by: Jiri Olsa 
LKML-Reference: <1254934835-363-3-git-send-email-jolsa@redhat.com>
Signed-off-by: Steven Rostedt 
Signed-off-by: Greg Kroah-Hartman