All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
To: linux-kernel@vger.kernel.org
Subject: 2.6.31: WARNING: at net/ipv4/af_inet.c:154 inet_sock_destruct+0x164/0x1c0()
Date: Wed, 30 Sep 2009 14:24:41 +0200	[thread overview]
Message-ID: <20090930122441.GB17974@charite.de> (raw)

This machine runs openvpn:

Sep 30 08:48:05 vpn-gw-int kernel: [1706466.259235] ------------[ cut here ]------------
Sep 30 08:48:05 vpn-gw-int kernel: [1706466.259246] WARNING: at net/ipv4/af_inet.c:154 inet_sock_destruct+0x164/0x1c0()
Sep 30 08:48:05 vpn-gw-int kernel: [1706466.259249] Hardware name: ProLiant DL360 G4p
Sep 30 08:48:05 vpn-gw-int kernel: [1706466.259251] Modules linked in: ipt_REJECT ipt_LOG xt_multiport tun xt_tcpudp xt_state iptable_nat nf_nat iptable_filter ip_tables x_tables nf_conntrack_ipv4 nf_defrag_ipv4 ipv6 psmouse nf_conntrack_ftp nf_conntrack tg3 libphy
Sep 30 08:48:05 vpn-gw-int kernel: [1706466.259274] Pid: 2286, comm: openvpn Not tainted 2.6.31 #1
Sep 30 08:48:05 vpn-gw-int kernel: [1706466.259276] Call Trace:
Sep 30 08:48:05 vpn-gw-int kernel: [1706466.259282]  [<c126d154>] ? inet_sock_destruct+0x164/0x1c0
Sep 30 08:48:05 vpn-gw-int kernel: [1706466.259288]  [<c10326fb>] ? warn_slowpath_common+0x6f/0xcd
Sep 30 08:48:05 vpn-gw-int kernel: [1706466.259292]  [<c126d154>] ? inet_sock_destruct+0x164/0x1c0
Sep 30 08:48:05 vpn-gw-int kernel: [1706466.259296]  [<c1032779>] ? warn_slowpath_null+0x20/0x3c
Sep 30 08:48:05 vpn-gw-int kernel: [1706466.259300]  [<c126d154>] ? inet_sock_destruct+0x164/0x1c0
Sep 30 08:48:05 vpn-gw-int kernel: [1706466.259305]  [<c128bdcb>] ? _spin_lock_bh+0x16/0x40
Sep 30 08:48:05 vpn-gw-int kernel: [1706466.259309]  [<c128bdcb>] ? _spin_lock_bh+0x16/0x40
Sep 30 08:48:05 vpn-gw-int kernel: [1706466.259314]  [<c121bc78>] ? __sk_free+0x21/0xd6
Sep 30 08:48:05 vpn-gw-int kernel: [1706466.259318]  [<c121be41>] ? sk_common_release+0x5b/0x97
Sep 30 08:48:05 vpn-gw-int kernel: [1706466.259321]  [<c126cc05>] ? inet_release+0x39/0x66
Sep 30 08:48:05 vpn-gw-int kernel: [1706466.259325]  [<c1218eaa>] ? sock_release+0x22/0x8d
Sep 30 08:48:05 vpn-gw-int kernel: [1706466.259329]  [<c1218f31>] ? sock_close+0x1c/0x42
Sep 30 08:48:05 vpn-gw-int kernel: [1706466.259334]  [<c10a125c>] ? __fput+0xd6/0x1e0
Sep 30 08:48:05 vpn-gw-int kernel: [1706466.259338]  [<c109dd34>] ? filp_close+0x41/0x72
Sep 30 08:48:05 vpn-gw-int kernel: [1706466.259342]  [<c109ddda>] ? sys_close+0x75/0xc0
Sep 30 08:48:05 vpn-gw-int kernel: [1706466.259347]  [<c1002ecf>] ? sysenter_do_call+0x12/0x26
Sep 30 08:48:05 vpn-gw-int kernel: [1706466.259350] ---[ end trace 4715d461fc27d993 ]---

-- 
Ralf Hildebrandt
  Geschäftsbereich IT | Abteilung Netzwerk
  Charité - Universitätsmedizin Berlin
  Campus Benjamin Franklin
  Hindenburgdamm 30 | D-12203 Berlin
  Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
  ralf.hildebrandt@charite.de | http://www.charite.de
	    

             reply	other threads:[~2009-09-30 12:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30 12:24 Ralf Hildebrandt [this message]
2009-09-30 12:33 ` 2.6.31: WARNING: at net/ipv4/af_inet.c:154 inet_sock_destruct+0x164/0x1c0() Ralf Hildebrandt
2009-09-30 12:36 ` Eric Dumazet
2009-10-01 11:08   ` Ralf Hildebrandt

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=20090930122441.GB17974@charite.de \
    --to=ralf.hildebrandt@charite.de \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.