From: John Dykstra <john.dykstra1@gmail.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: netdev@vger.kernel.org
Subject: Re: WARNING: at net/ipv4/af_inet.c:155 inet_sock_destruct+0x122/0x13a()
Date: Tue, 04 Aug 2009 20:04:57 +0000 [thread overview]
Message-ID: <1249416297.7174.10.camel@Maple> (raw)
In-Reply-To: <4A76A009.40605@wpkg.org>
On Mon, 2009-08-03 at 10:30 +0200, Tomasz Chmielewski wrote:
> After upgrading from 2.6.29.1 to 2.6.30.4, I'm getting these warnings in dmesg.
>
> Let me know if you need more info.
>
> Other than that, the device seems to work stable.
>
> ------------[ cut here ]------------
> WARNING: at net/ipv4/af_inet.c:155 inet_sock_destruct+0x122/0x13a()
> Hardware name: Altos G510
> Modules linked in: nfs nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs tun bitrev crc32 bonding lm75 adm9240 adm1026 hwmon_vid hwmon i2c_piix4 i2c_core dm_crypt dm_mirror dm_region_hash dm_log dm_snapshot dm_mod e1000 tg3 libphy
> Pid: 2222, comm: openvpn Not tainted 2.6.30.4-1 #4
> Call Trace:
> [<4011f018>] ? warn_slowpath_common+0x5e/0x8a
> [<4011f04e>] ? warn_slowpath_null+0xa/0xc
> [<402b5d64>] ? inet_sock_destruct+0x122/0x13a
> [<402796a4>] ? sk_free+0x10/0xa7
> [<402b5964>] ? inet_release+0x3f/0x44
> [<4027751b>] ? sock_release+0x11/0x52
> [<40277575>] ? sock_close+0x19/0x1c
> [<40164026>] ? __fput+0xa6/0x149
> [<40161989>] ? filp_close+0x4e/0x54
> [<401619f5>] ? sys_close+0x66/0x9c
> [<401027c8>] ? sysenter_do_call+0x12/0x26
> ---[ end trace bdfe445acbab5307 ]---
> ------------[ cut here ]------------
> WARNING: at net/ipv4/af_inet.c:155 inet_sock_destruct+0x122/0x13a()
> Hardware name: Altos G510
> Modules linked in: nfs nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs tun bitrev crc32 bonding lm75 adm9240 adm1026 hwmon_vid hwmon i2c_piix4 i2c_core dm_crypt dm_mirror dm_region_hash dm_log dm_snapshot dm_mod e1000 tg3 libphy
> Pid: 2222, comm: openvpn Tainted: G W 2.6.30.4-1 #4
> Call Trace:
> [<4011f018>] ? warn_slowpath_common+0x5e/0x8a
> [<4011f04e>] ? warn_slowpath_null+0xa/0xc
> [<402b5d64>] ? inet_sock_destruct+0x122/0x13a
> [<402796a4>] ? sk_free+0x10/0xa7
> [<402b5964>] ? inet_release+0x3f/0x44
> [<4027751b>] ? sock_release+0x11/0x52
> [<40277575>] ? sock_close+0x19/0x1c
> [<40164026>] ? __fput+0xa6/0x149
> [<40161989>] ? filp_close+0x4e/0x54
> [<401619f5>] ? sys_close+0x66/0x9c
> [<401027c8>] ? sysenter_do_call+0x12/0x26
> ---[ end trace bdfe445acbab5308 ]---
> ------------[ cut here ]------------
> WARNING: at net/ipv4/af_inet.c:155 inet_sock_destruct+0x122/0x13a()
> Hardware name: Altos G510
> Modules linked in: nfs nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs tun bitrev crc32 bonding lm75 adm9240 adm1026 hwmon_vid hwmon i2c_piix4 i2c_core dm_crypt dm_mirror dm_region_hash dm_log dm_snapshot dm_mod e1000 tg3 libphy
> Pid: 2222, comm: openvpn Tainted: G W 2.6.30.4-1 #4
> Call Trace:
> [<4011f018>] ? warn_slowpath_common+0x5e/0x8a
> [<4011f04e>] ? warn_slowpath_null+0xa/0xc
> [<402b5d64>] ? inet_sock_destruct+0x122/0x13a
> [<402796a4>] ? sk_free+0x10/0xa7
> [<402b5964>] ? inet_release+0x3f/0x44
> [<4027751b>] ? sock_release+0x11/0x52
> [<40277575>] ? sock_close+0x19/0x1c
> [<40164026>] ? __fput+0xa6/0x149
> [<40161989>] ? filp_close+0x4e/0x54
> [<401619f5>] ? sys_close+0x66/0x9c
> [<401027c8>] ? sysenter_do_call+0x12/0x26
> ---[ end trace bdfe445acbab5309 ]---
Is this an openvpn server or client?
Does the warning fire on each authentication, or while the tunnel is
up?
Are you tunneling over UDP or TCP?
Your kernel config, network configuration details and openvpn
configuration might be useful.
Thanks!
-- John
next prev parent reply other threads:[~2009-08-04 20:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 8:30 WARNING: at net/ipv4/af_inet.c:155 inet_sock_destruct+0x122/0x13a() Tomasz Chmielewski
2009-08-04 0:38 ` John Dykstra
2009-08-04 4:20 ` David Miller
2009-08-04 6:18 ` Eric Dumazet
2009-08-12 20:00 ` Vlad Yasevich
2009-08-13 15:21 ` John Dykstra
2009-08-13 17:04 ` Vlad Yasevich
2009-08-13 18:16 ` Tomasz Chmielewski
2009-08-04 20:04 ` John Dykstra [this message]
2009-08-04 20:35 ` Tomasz Chmielewski
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=1249416297.7174.10.camel@Maple \
--to=john.dykstra1@gmail.com \
--cc=mangoo@wpkg.org \
--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).