From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Eric Sesterhenn <snakebyte@gmx.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net, ilpo.jarvinen@helsinki.fi
Subject: Re: Slab Corruption with ipv6 and tcp6fuzz
Date: Fri, 25 Apr 2008 17:09:46 +0400 [thread overview]
Message-ID: <20080425130946.GA1019@2ka.mipt.ru> (raw)
In-Reply-To: <20080425125230.GA12343@alice>
On Fri, Apr 25, 2008 at 02:52:30PM +0200, Eric Sesterhenn (snakebyte@gmx.de) wrote:
> > > [ 215.103103] [<c0671e3b>] tcp_v6_do_rcv+0x33b/0xcd0
> >
> > So far can you run kernel with debug turned on and provide output of
> > gdb ./vmlinux
> > l *(tcp_v6_do_rcv+0x33b)
>
> l *(tcp_v6_do_rcv+0x33b)
> Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
> (gdb) l *(tcp_v6_do_rcv+0x33b)
> 0xc0671e3b is in tcp_v6_do_rcv (net/ipv6/tcp_ipv6.c:1670).
> 1665 reset:
> 1666 tcp_v6_send_reset(sk, skb);
> 1667 discard:
> 1668 if (opt_skb)
> 1669 __kfree_skb(opt_skb);
> 1670 kfree_skb(skb);
> 1671 return 0;
> 1672 csum_err:
> 1673 TCP_INC_STATS_BH(TCP_MIB_INERRS);
> 1674 goto discard;
Well, first possible error path:
tcp_v6_do_rcv()->tcp_rcv_established(), the latter goes to step5, where
eventually skb can be freed via tcp_data_queue() (drop: label), then if
check for tcp_defer_accept_check() returns true and thus
tcp_rcv_established() returns -1, which forces tcp_v6_do_rcv() to jump
to reset: label, which in turn will pass through discard: label and free
the same skb again.
> Here is the programm itself...
I will work on this this weekend, thank you.
--
Evgeniy Polyakov
next prev parent reply other threads:[~2008-04-25 13:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 14:27 Slab Corruption with ipv6 and tcp6fuzz Eric Sesterhenn
2008-04-24 19:48 ` Ilpo Järvinen
2008-04-24 21:13 ` Evgeniy Polyakov
2008-04-25 12:52 ` Eric Sesterhenn
2008-04-25 13:09 ` Evgeniy Polyakov [this message]
2008-04-26 16:05 ` Evgeniy Polyakov
2008-04-27 6:05 ` David Miller
2008-04-27 13:25 ` Patrick McManus
2008-04-27 15:32 ` Eric Sesterhenn
2008-04-27 16:48 ` Patrick McManus
2008-04-27 22:27 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080425130946.GA1019@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=netdev@vger.kernel.org \
--cc=snakebyte@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.