From: Arjan van de Ven <arjan@linux.intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Petr Vandrovec <vandrove@vc.cvut.cz>,
netdev@vger.kernel.org, mingo@elte.hu, davem@davemloft.net
Subject: Re: IPV6 possible recursive locking
Date: Fri, 04 Aug 2006 17:56:27 -0700 [thread overview]
Message-ID: <44D3ECBB.6060901@linux.intel.com> (raw)
In-Reply-To: <E1G99sr-0004a2-00@gondolin.me.apana.org.au>
Herbert Xu wrote:
>> [<ffffffff812a6ac4>] sk_clone+0xd4/0x350
>> [<ffffffff812f6fb1>] inet_csk_clone+0x11/0x70
>> [<ffffffff81300b94>] tcp_create_openreq_child+0x24/0x480
>> [<ffffffff8136e7c2>] tcp_v6_syn_recv_sock+0x2c2/0x6f0
>> [<ffffffff81301219>] tcp_check_req+0x229/0x3a0
>> [<ffffffff8136d7bd>] tcp_v6_do_rcv+0x17d/0x400
>> [<ffffffff81370215>] tcp_v6_rcv+0x7e5/0x850
>
> Yes this is a known problem. The lock validator needs to learn how
> to distinguish between parent and child sockets.
Hmm I remember fixing sk_clone before.. or was that skb_clone, I'd have ot check.
Anyway I'll check this out either later today or tomorrow in more detail
and will send a patch.
next prev parent reply other threads:[~2006-08-05 0:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 20:31 IPV6 possible recursive locking Petr Vandrovec
2006-08-05 0:19 ` Herbert Xu
2006-08-05 0:56 ` Arjan van de Ven [this message]
2006-08-05 1:12 ` Herbert Xu
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=44D3ECBB.6060901@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
/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).