From: "David S. Miller" <davem@redhat.com>
To: green@namesys.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: unix sockets problems in 2.5.4-pre6?
Date: Mon, 11 Feb 2002 00:49:53 -0800 (PST) [thread overview]
Message-ID: <20020211.004953.74751936.davem@redhat.com> (raw)
In-Reply-To: <20020211111904.A955@namesys.com>
In-Reply-To: <20020211111904.A955@namesys.com>
From: Oleg Drokin <green@namesys.com>
Date: Mon, 11 Feb 2002 11:19:04 +0300
Just tried 2.5.4-pre6 and got hung postfix "master" process which I cannot
kill in RUNNABLE state. Here is traces of all postfix processes at the time:
pickup Z C212E180 48 522 520 523 (L-TLB)
Call Trace: [do_exit+745/784] [sys_exit+14/16] [syscall_call+7/11]
qmgr S F70FBF30 48 523 520 524 522 (NOTLB)
Call Trace: [schedule_timeout+128/160] [process_timeout+0/16] [do_select+470/544] [sys_select+832/1152] [syscall_call+7/11]
tlsmgr S F70F5F30 8944 524 520 523 (NOTLB)
Call Trace: [schedule_timeout+128/160] [process_timeout+0/16] [do_select+470/544] [sys_select+832/1152] [syscall_call+7/11]
master R F773F744 48 520 900 524 (NOTLB)
Call Trace: [__write_lock_failed+9/32] [.text.lock.open+71/137] [unix_create+92/112] [sock_map_fd+12/304] [select_bits_free+10/16]
[sys_socket+29/96] [sys_socket+48/96] [sys_socketcall+99/512] [syscall_call+7/11]
Hope this will help someone to nail a problem
It doesn't help. You need to find the backtrace of the other process
holding the lock the AF_UNIX code wants as well, dumping just these
few processes isn't enough.
Franks a lot,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2002-02-11 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 8:19 unix sockets problems in 2.5.4-pre6? Oleg Drokin
2002-02-11 8:49 ` David S. Miller [this message]
2002-02-11 8:59 ` Oleg Drokin
2002-02-11 13:02 ` David S. Miller
2002-02-11 13:37 ` Oleg Drokin
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=20020211.004953.74751936.davem@redhat.com \
--to=davem@redhat.com \
--cc=green@namesys.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox