[Top] [All Lists]

Re: [PATCH] IPV6_CHECKSUM socket option can corrupt kernel memory

To: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [PATCH] IPV6_CHECKSUM socket option can corrupt kernel memory
From: David Stevens <dlstevens@xxxxxxxxxx>
Date: Thu, 14 Apr 2005 12:36:46 -0600
Cc: davem@xxxxxxxxxxxxx, netdev@xxxxxxxxxxx, yoshfuji@xxxxxxxxxxxxxx
In-reply-to: <>
Sender: netdev-bounce@xxxxxxxxxxx
I'm still looking at your patch.

Below is a piece of my original patch that I've separated out to make sure
it doesn't get lost in this discussion. It's the fix for the bug that 
triggered all
of this and the real cause of the panic for the ordinary raw-socket cases, 
nr_frags is supposed to be "0". Attached and in-line below.

A couple comments initially on your patch: multiple packet support I don't
think is needed here (in sendmsg). I agree it's good to put it in for 
possible uses, but IPV6_CHECKSUM doesn't need it, as far as I can tell.

How about a loop instead of a recursive call? If the list is long enough
and the architecture eats stack a lot of stack space on function calls,
that could be a problem.

The fix part of the patch:

Signed-off-by: David L Stevens <dlstevens@xxxxxxxxxx>

--- linux-       2005-04-07 11:57:32.000000000 
+++ linux-     2005-04-12 15:05:00.000000000 
@@ -771,8 +790,11 @@ back_from_confirm:
                if (err)
-               else if (!(msg->msg_flags & MSG_MORE))
+               else if (!(msg->msg_flags & MSG_MORE)) {
                        err = rawv6_push_pending_frames(sk, &fl, rp, len);
+                       if (err)
+                               ip6_flush_pending_frames(sk);
+               }
        ip6_dst_store(sk, dst,

Attachment: rawv6-2.patch
Description: Binary data

<Prev in Thread] Current Thread [Next in Thread>