From: Evgeniy Polyakov <zbr@ioremap.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mike@nauticaltech.com, bugme-daemon@bugzilla.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [Bugme-new] [Bug 12201] New: long wait in call_usermodehelper() / queue_work() / wait_for_completion()
Date: Fri, 12 Dec 2008 01:51:58 +0300 [thread overview]
Message-ID: <20081211225158.GA2169@ioremap.net> (raw)
In-Reply-To: <20081211143758.510b51b6.akpm@linux-foundation.org>
Hi.
On Thu, Dec 11, 2008 at 02:37:58PM -0800, Andrew Morton (akpm@linux-foundation.org) wrote:
> > If I write a small pilot program that calls socket(PF_NETLINK, SOCK_RAW,
> > NETLINK_AUDIT), it will delay by 1-2 seconds 100% of the time (assuming server
> > has been online for a while). Certain protocol types given to socket() have
> > zero delay (because no module needs to be loaded).
> >
> > Steps to reproduce:
> > Once server has been online for a while, a simple call to socket(PF_NETLINK,
> > SOCK_RAW, NETLINK_AUDIT) shows the problem.
>
> OK, weird.
>
> Please get sysrq working then get us a task trace, so we can see who is
> sleeping where. Do this:
>
>
> - run your "small pilot program"
Or send it to us and we will quickly fix the bug :)
Thank you!
--
Evgeniy Polyakov
next prev parent reply other threads:[~2008-12-11 22:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-12201-10286@http.bugzilla.kernel.org/>
2008-12-11 22:37 ` [Bugme-new] [Bug 12201] New: long wait in call_usermodehelper() / queue_work() / wait_for_completion() Andrew Morton
2008-12-11 22:48 ` Kay Sievers
2008-12-12 19:47 ` Michael Spiegle
2008-12-11 22:51 ` Evgeniy Polyakov [this message]
2008-12-11 23:05 ` Evgeniy Polyakov
2008-12-12 19:51 ` Michael Spiegle
2008-12-12 19:42 ` Michael Spiegle
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=20081211225158.GA2169@ioremap.net \
--to=zbr@ioremap.net \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@nauticaltech.com \
--cc=netdev@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).