linux-toradex.git/net/ipv6/raw.c, branch v2.6.16.30

[IPV6] Don't store dst_entry for RAW socket

2006-02-13T23:56:13+00:00

Signed-off-by: Nicolas DICHTEL 
Signed-off-by: David S. Miller

[PATCH] remove bogus asm/bug.h includes.

2006-02-08T01:56:35+00:00

A bunch of asm/bug.h includes are both not needed (since it will get
pulled anyway) and bogus (since they are done too early).  Removed.

Signed-off-by: Al Viro

[IP]: Simplify and consolidate MSG_PEEK error handling

2006-01-03T21:10:41+00:00

When a packet is obtained from skb_recv_datagram with MSG_PEEK enabled
it is left on the socket receive queue.  This means that when we detect
a checksum error we have to be careful when trying to free the packet
as someone could have dequeued it in the time being.

Currently this delicate logic is duplicated three times between UDPv4,
UDPv6 and RAWv6.  This patch moves them into a one place and simplifies
the code somewhat.

This is based on a suggestion by Eric Dumazet.

Signed-off-by: Herbert Xu 
Signed-off-by: David S. Miller

Merge git://git.skbuff.net/gitroot/yoshfuji/linux-2.6.14+advapi-fix/

2005-11-21T04:52:16+00:00

[IPV6]: Fix sending extension headers before and including routing header.

2005-11-20T03:23:18+00:00

Based on suggestion from Masahide Nakamura .

Signed-off-by: YOSHIFUJI Hideaki

[NET]: Detect hardware rx checksum faults correctly

2005-11-10T21:01:24+00:00

Here is the patch that introduces the generic skb_checksum_complete
which also checks for hardware RX checksum faults.  If that happens,
it'll call netdev_rx_csum_fault which currently prints out a stack
trace with the device name.  In future it can turn off RX checksum.

I've converted every spot under net/ that does RX checksum checks to
use skb_checksum_complete or __skb_checksum_complete with the
exceptions of:

* Those places where checksums are done bit by bit.  These will call
netdev_rx_csum_fault directly.

* The following have not been completely checked/converted:

ipmr
ip_vs
netfilter
dccp

This patch is based on patches and suggestions from Stephen Hemminger
and David S. Miller.

Signed-off-by: Herbert Xu 
Signed-off-by: David S. Miller

[NETFILTER]: Add nf_conntrack subsystem.

2005-11-10T00:38:16+00:00

The existing connection tracking subsystem in netfilter can only
handle ipv4.  There were basically two choices present to add
connection tracking support for ipv6.  We could either duplicate all
of the ipv4 connection tracking code into an ipv6 counterpart, or (the
choice taken by these patches) we could design a generic layer that
could handle both ipv4 and ipv6 and thus requiring only one sub-protocol
(TCP, UDP, etc.) connection tracking helper module to be written.

In fact nf_conntrack is capable of working with any layer 3
protocol.

The existing ipv4 specific conntrack code could also not deal
with the pecularities of doing connection tracking on ipv6,
which is also cured here.  For example, these issues include:

1) ICMPv6 handling, which is used for neighbour discovery in
   ipv6 thus some messages such as these should not participate
   in connection tracking since effectively they are like ARP
   messages

2) fragmentation must be handled differently in ipv6, because
   the simplistic "defrag, connection track and NAT, refrag"
   (which the existing ipv4 connection tracking does) approach simply
   isn't feasible in ipv6

3) ipv6 extension header parsing must occur at the correct spots
   before and after connection tracking decisions, and there were
   no provisions for this in the existing connection tracking
   design

4) ipv6 has no need for stateful NAT

The ipv4 specific conntrack layer is kept around, until all of
the ipv4 specific conntrack helpers are ported over to nf_conntrack
and it is feature complete.  Once that occurs, the old conntrack
stuff will get placed into the feature-removal-schedule and we will
fully kill it off 6 months later.

Signed-off-by: Yasuyuki Kozakai 
Signed-off-by: Harald Welte 
Signed-off-by: Arnaldo Carvalho de Melo

[PATCH] raw_sendmsg DoS on 2.6

2005-09-20T01:45:42+00:00

Fix unchecked __get_user that could be tricked into generating a
memory read on an arbitrary address.  The result of the read is not
returned directly but you may be able to divine some information about
it, or use the read to cause a crash on some architectures by reading
hardware state.  CAN-2004-2492.

Fix from Al Viro, ack from Dave Miller.

Signed-off-by: Linus Torvalds

[XFRM]: Always release dst_entry on error in xfrm_lookup

2005-09-08T22:11:55+00:00

Signed-off-by: Patrick McHardy 
Signed-off-by: David S. Miller

[IPV6]: Support IPV6_{RECV,}TCLASS socket options / ancillary data.

2005-09-08T01:19:03+00:00

Based on patch from David L Stevens 

Signed-off-by: David L Stevens 
Signed-off-by: YOSHIFUJI Hideaki