From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: "David S. Miller" <davem@redhat.com>
Cc: manfred@colorfullife.com, netdev@oss.sgi.com, akpm@digeo.com
Subject: Re: oops in tcp_v4_rcv.
Date: Wed, 28 May 2003 22:50:20 -0300 [thread overview]
Message-ID: <20030529015020.GS12434@conectiva.com.br> (raw)
In-Reply-To: <20030528.184054.78710412.davem@redhat.com>
Em Wed, May 28, 2003 at 06:40:54PM -0700, David S. Miller escreveu:
> From: Manfred Spraul <manfred@colorfullife.com>
> Date: Thu, 29 May 2003 03:15:57 +0200
>
> I think I understand now what causes the crash:
> The tcp_ehash assumes that the entries are of the type 'struct inet_sock'.
> But the actual entry is of the type tcp_tw_bucket. And 'sk->inet.daddr'
> is not shared between both structures.
>
> Thanks for figuring this out. Indeed, I had suspected the
> sock layout change Arnaldo did early in 2.5.x as the main
> possible suspect.
>
> I'll try to fix this.
I'm as well looking at this, longstanding bug :-\
- Arnaldo
next prev parent reply other threads:[~2003-05-29 1:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3ED54DBC.4020203@colorfullife.com>
2003-05-29 1:15 ` oops in tcp_v4_rcv Manfred Spraul
2003-05-29 1:40 ` David S. Miller
2003-05-29 1:50 ` Arnaldo Carvalho de Melo [this message]
2003-05-29 1:51 ` David S. Miller
2003-05-29 2:00 ` Arnaldo Carvalho de Melo
2003-05-29 3:06 ` David S. 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=20030529015020.GS12434@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=akpm@digeo.com \
--cc=davem@redhat.com \
--cc=manfred@colorfullife.com \
--cc=netdev@oss.sgi.com \
/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).