linux-toradex.git/net, branch v2.6.22.5

softmac: Fix deadlock of wx_set_essid with assoc work

2007-08-15T16:25:09+00:00

The essid wireless extension does deadlock against the assoc mutex,
as we don't unlock the assoc mutex when flushing the workqueue, which
also holds the lock.

Signed-off-by: Michael Buesch 
Signed-off-by: Greg Kroah-Hartman

Netfilter: Fix logging regression

2007-08-09T21:27:46+00:00

[NETFILTER]: Fix logging regression

Loading one of the LOG target fails if a different target has already
registered itself as backend for the same family. This can affect the
ipt_LOG and ipt_ULOG modules when both are loaded.

Reported and tested by: 
Upstream-commit: 7e2acc7e

Signed-off-by: Patrick McHardy 
Signed-off-by: Greg Kroah-Hartman

IPV6: /proc/net/anycast6 unbalanced inet6_dev refcnt

2007-08-09T21:27:46+00:00

Reading /proc/net/anycast6 when there is no anycast address
on an interface results in an ever-increasing inet6_dev reference
count, as well as a reference to the netdevice you can't get rid of.

Signed-off-by: David S. Miller 
Cc: Marcus Meissner 
Signed-off-by: Greg Kroah-Hartman

nf_conntrack: don't track locally generated special ICMP error

2007-08-09T21:27:46+00:00

[NETFILTER]: nf_conntrack: don't track locally generated special ICMP error

The conntrack assigned to locally generated ICMP error is usually the one
assigned to the original packet which has caused the error. But if
the original packet is handled as invalid by nf_conntrack, no conntrack
is assigned to the original packet. Then nf_ct_attach() cannot assign
any conntrack to the ICMP error packet. In that case the current
nf_conntrack_icmp assigns appropriate conntrack to it. But the current
code mistakes the direction of the packet. As a result, NAT code mistakes
the address to be mangled.

To fix the bug, this changes nf_conntrack_icmp not to assign conntrack
to such ICMP error. Actually no address is necessary to be mangled
in this case.

Spotted by Jordan Russell.

Signed-off-by: Yasuyuki Kozakai 

Upstream commit ID: 130e7a83d7ec8c5c673225e0fa8ea37b1ed507a5

Signed-off-by: Patrick McHardy 
Signed-off-by: Greg Kroah-Hartman

Keep rfcomm_dev on the list until it is freed

2007-08-09T21:27:46+00:00

This patch changes the RFCOMM TTY release process so that the TTY is kept
on the list until it is really freed. A new device flag is used to keep
track of released TTYs.

Signed-off-by: Ville Tervo 
Signed-off-by: Marcel Holtmann 
Signed-off-by: Greg Kroah-Hartman

Hangup TTY before releasing rfcomm_dev

2007-08-09T21:27:46+00:00

The core problem is that RFCOMM socket layer ioctl can release
rfcomm_dev struct while RFCOMM TTY layer is still actively using
it. Calling tty_vhangup() is needed for a synchronous hangup before
rfcomm_dev is freed.

Addresses the oops at http://bugzilla.kernel.org/show_bug.cgi?id=7509

Acked-by: Alan Cox 
Signed-off-by: Marcel Holtmann 
Signed-off-by: Greg Kroah-Hartman

nfsd: fix possible oops on re-insertion of rpcsec_gss modules

2007-08-09T21:27:42+00:00

The handling of the re-registration case is wrong here; the "test" that was
returned from auth_domain_lookup will not be used again, so that reference
should be put.  And auth_domain_lookup never did anything with "new" in
this case, so we should just clean it up ourself.

Thanks to Akinobu Mita for bug report, analysis, and testing.

Cc: Akinobu Mita 
Signed-off-by: "J. Bruce Fields" 
Cc: Neil Brown 
Cc: Trond Myklebust 
Signed-off-by: Andrew Morton 
Signed-off-by: Greg Kroah-Hartman

softmac: Fix ESSID problem

2007-08-09T21:27:38+00:00

Victor Porton reported that the SoftMAC layer had random problem when setting the ESSID :
http://bugzilla.kernel.org/show_bug.cgi?id=8686 After investigation, it turned out to be
worse, the SoftMAC layer is left in an inconsistent state. The fix is pretty trivial.

Signed-off-by: Jean Tourrilhes 
Acked-by: Michael Buesch 
Acked-by: Larry Finger 
Acked-by: John W. Linville 
Signed-off-by: Greg Kroah-Hartman

Fix TCP IPV6 MD5 bug.

2007-08-09T21:27:30+00:00

[TCPv6] MD5SIG: Ensure to reset allocation count to avoid panic.

After clearing all passwords for IPv6 peers, we need to
set allocation count to zero as well as we free the storage.
Otherwise, we panic when a user trys to (re)add a password.

Discovered and fixed by MIYAJIMA Mitsuharu .

Signed-off-by: YOSHIFUJI Hideaki 
Signed-off-by: David S. Miller 
Signed-off-by: Greg Kroah-Hartman

Fix ipv6 tunnel endianness bug.

2007-08-09T21:27:29+00:00

[IPV6]: endianness bug in ip6_tunnel

Signed-off-by: Al Viro 
Signed-off-by: David S. Miller 
Signed-off-by: Greg Kroah-Hartman