LKML Archive on
help / color / mirror / Atom feed
From: Stefan Richter <>
To: Denys Fedoryshchenko <>
Cc: Peter Zijlstra <>,
Subject: Re: possible recursive locking, 2.6.24-rc7
Date: Mon, 14 Jan 2008 19:15:18 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Denys Fedoryshchenko wrote:
> I cannot reproduce, it is happened with rtorrent just randomly. But i will
> patch and keep watching.
> On Sun, 13 Jan 2008 19:44:26 +0100, Peter Zijlstra wrote
>> On Sun, 2008-01-13 at 17:22 +0100, Peter Zijlstra wrote:
>> > It's epoll, this is a known issue and will be fixed soon. Thanks for
>> > reporting.
>> If its easy for you to reproduce, would you mind giving the following
>> patch a spin?

I may have a way to trigger another epoll "recursive-locking" trace at
will with current firewire development code.  Will try the annotation
patch when I have time.
Stefan Richter
-=====-==--- ---= -===-

      reply	other threads:[~2008-01-14 18:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-13 15:51 possible recursive locking, 2.6.24-rc7 Denys Fedoryshchenko
2008-01-13 16:22 ` Peter Zijlstra
2008-01-13 18:44   ` Peter Zijlstra
2008-01-13 19:25     ` Denys Fedoryshchenko
2008-01-14 18:15       ` Stefan Richter [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).