From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Josh Boyer <jwboyer@gmail.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] eventpoll: possible recursive locking detected
Date: Thu, 27 Oct 2011 15:53:48 +0300 [thread overview]
Message-ID: <20111027125347.GA3373@swordfish> (raw)
In-Reply-To: <CA+5PVA51Rdd-33v-2pxdzXpQGnMrL+PYkzeXqM1R2fxXCK=Bqg@mail.gmail.com>
On (10/27/11 08:46), Josh Boyer wrote:
> Nelson Elhage posted a patch to fix this for the 3.1 merge window and
> it never went in. You can find it here:
>
> http://thread.gmane.org/gmane.linux.kernel/1177210
>
> Not sure why it hasn't been pushed upstream yet.
>
Oh, good, thanks for pointing out.
Sergey
prev parent reply other threads:[~2011-10-27 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 12:14 [PATCH] eventpoll: possible recursive locking detected Sergey Senozhatsky
2011-10-27 12:46 ` Josh Boyer
2011-10-27 12:53 ` Sergey Senozhatsky [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=20111027125347.GA3373@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=jwboyer@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).