From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: Sridhar Samudrala <sri@us.ibm.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: very strange inet_sock corruption with rpc
Date: Thu, 26 Apr 2007 08:52:34 -0400 [thread overview]
Message-ID: <4630A092.8000504@hp.com> (raw)
In-Reply-To: <1177539237.21594.3.camel@w-sridhar2.beaverton.ibm.com>
Sridhar Samudrala wrote:
>> The corruption is triggered after about 10 minutes of running the following
>> script:
>>
>> nfspath = $1
>> localpath = $2
>> while true; do
>> mount "$nfspath" "$localpath"
>> sleep 5
>> cp /boot/vmlinuz "$localpath"
>> sleep 5
>> rm $localpath/vmlinuz
>> sleep 5
>> umount "$localpath"
>> done
>>
>>
>> And looks like this:
>>
>> sk2 might be corrupt. Info:
>> sk2 = ffff8100f004d080
>> tb->port = 844
>> inet_sk(sk2)->num = 61695
>> inet_sk(sk2)->foo = 24242424243f243f
>> inet_sk(sk2)->bar = 3f24243f
>> BUG: at net/ipv4/inet_connection_sock.c:58 inet_csk_bind_conflict()
>>
>> Call Trace:
>> [<ffffffff803cc591>] inet_csk_bind_conflict+0xcb/0x178
>> [<ffffffff803cc4c6>] inet_csk_bind_conflict+0x0/0x178
>> [<ffffffff803cc2ff>] inet_csk_get_port+0x11a/0x1ef
>> [<ffffffff803ddf51>] inet_bind+0x117/0x1f5
>> [<ffffffff88184e13>] :sunrpc:xs_bindresvport+0x4e/0xbf
>> [<ffffffff881853a4>] :sunrpc:xs_tcp_connect_worker+0x0/0x2a0
>> [<ffffffff88185433>] :sunrpc:xs_tcp_connect_worker+0x8f/0x2a0
>
> If you are using NFS over UDP, why is a TCP routine
> getting called by sunrpc?
No clue. ;) My guess is that is has something to do with RPC
itself, but this is the question I keep asking myself as well.
I don't have an answer for it yet.
Just for completeness, here is the mount line from fstab:
host:/export /mnt nfs soft,noatime,rsize=8192,wsize=8192,timeo=14,intr,auto 0 0
-vlad
>
>> [<ffffffff80248bd3>] run_workqueue+0x8f/0x137
>> [<ffffffff80245687>] worker_thread+0x0/0x14a
>> [<ffffffff8024579b>] worker_thread+0x114/0x14a
>> [<ffffffff8027e544>] default_wake_function+0x0/0xe
>> [<ffffffff8022ff49>] kthread+0xd1/0x100
>> [<ffffffff80258f68>] child_rip+0xa/0x12
>> [<ffffffff8022fe78>] kthread+0x0/0x100
>> [<ffffffff80258f5e>] child_rip+0x0/0x12
next prev parent reply other threads:[~2007-04-26 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 21:03 very strange inet_sock corruption with rpc Vlad Yasevich
2007-04-25 22:13 ` Sridhar Samudrala
2007-04-26 12:52 ` Vlad Yasevich [this message]
2007-04-26 6:49 ` Olaf Kirch
2007-04-26 13:00 ` Vlad Yasevich
2007-04-26 13:00 ` Arnaldo Carvalho de Melo
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=4630A092.8000504@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=netdev@vger.kernel.org \
--cc=sri@us.ibm.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).