From: Eric Sesterhenn <snakebyte@gmx.de>
To: Patrick McManus <mcmanus@ducksong.com>
Cc: David Miller <davem@davemloft.net>,
johnpol@2ka.mipt.ru, netdev@vger.kernel.org,
ilpo.jarvinen@helsinki.fi, dada1@cosmosbay.com
Subject: Re: Slab Corruption with ipv6 and tcp6fuzz
Date: Sun, 27 Apr 2008 17:32:11 +0200 [thread overview]
Message-ID: <20080427153211.GA6182@alice> (raw)
In-Reply-To: <1209302742.29301.137.camel@tng>
* Patrick McManus (mcmanus@ducksong.com) wrote:
> I'll take a look asap - thanks for the cc:, I've been away.
Evgeniys patch fixes the issue for me and i see no more corruptions.
Eric
> > > Ok, I can not reproduce it, so lets try hard way.
> > > Can you test attached patch, its idea is described above and I checked
> > > multiple times, that it is forbidden to free skb and return non-zero
> > > value from tcp_rcv_established(). This behaviour was introduced with TCP
> > > defer accept changes in 2.6.25 with
> > > ec3c0982a2dd1e671bad8e9d26c28dcba0039d87 commit.
> > >
> > > Please test. This bug affects both ipv6 and ipv4 code actually.
> > >
> > > diff --git a/net/ipv4/tcp_input.c b/net/ipv4/tcp_input.c
> > > index ac9b848..0298f80 100644
> > > --- a/net/ipv4/tcp_input.c
> > > +++ b/net/ipv4/tcp_input.c
> > > @@ -4925,8 +4925,7 @@ step5:
> > > tcp_data_snd_check(sk);
> > > tcp_ack_snd_check(sk);
> > >
> > > - if (tcp_defer_accept_check(sk))
> > > - return -1;
> > > + tcp_defer_accept_check(sk);
> > > return 0;
> > >
> > > csum_error:
next prev parent reply other threads:[~2008-04-27 15:32 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
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 [this message]
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=20080427153211.GA6182@alice \
--to=snakebyte@gmx.de \
--cc=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=johnpol@2ka.mipt.ru \
--cc=mcmanus@ducksong.com \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).