netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, Jike Song <albcamus@gmail.com>
Subject: Re: [BUG] af_unix race in close?
Date: Wed, 23 Sep 2009 22:56:11 -0700	[thread overview]
Message-ID: <20090923225611.425f40e5@nehalam> (raw)
In-Reply-To: <4ABAF727.8060905@gmail.com>

On Thu, 24 Sep 2009 06:35:51 +0200
Eric Dumazet <eric.dumazet@gmail.com> wrote:

> inted (2.6.31-0.125.4.2.rc5.git2.fc12.i686 #1) AOA110
> > EIP: 0060:[] EFLAGS: 00010202 CPU: 0
> > EIP is at unix_write_space+0x45/0x87
> > EAX: 6b6b6b6b EBX: ec988780 ECX: 00000000 EDX: 6b6b6b8f
> > ESI: ec988950 EDI: ffffff20 EBP: ec941e28 ESP: ec941e1c
> >  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
> > Process metacity (pid: 6809, ti=ec940000 task=e63095c0 task.ti=ec940000)
> > Stack:
> >  37dc7803 ec988780 000000e1 ec941e40 c0772142 37dc7803 dcc1c900 dcc1c900  
> > <0> c07f6a02 ec941e50 c0775766 37dc7803 dcc1c900 ec941e60 c07754ae 37dc7803
> > <0> dcc1c900 ec941e78 c07755db 37dc7803 ec98b0c0 dcc1c900 00000000 ec941ea0  
> > Call Trace:
> >  [] ? sock_wfree+0x44/0x68
> >  [] ? unix_release_sock+0x182/0x1e0
> >  [] ? skb_release_head_state+0x6c/0xcb
> >  [] ? __kfree_skb+0x20/0x94
> >  [] ? kfree_skb+0x68/0x7f
> >  [] ? unix_release_sock+0x182/0x1e0
> >  [] ? unix_release+0x2f/0x42
> >  [] ? sock_release+0x29/0x7f
> >  [] ? sock_close+0x30/0x45
> >  [] ? __fput+0x101/0x1a2

Good thanks. It should probably go up to stable as well.

      reply	other threads:[~2009-09-24  5:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-23 23:54 [BUG] af_unix race in close? Stephen Hemminger
2009-09-24  4:35 ` Eric Dumazet
2009-09-24  5:56   ` Stephen Hemminger [this message]

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=20090923225611.425f40e5@nehalam \
    --to=shemminger@vyatta.com \
    --cc=albcamus@gmail.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --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).