From: Linus Torvalds <torvalds@linux-foundation.org>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Davi Arnaut <davi@haxent.com.br>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] timerfd/eventfd context lock doesn't protect against poll_wait
Date: Fri, 18 May 2007 07:45:07 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0705180744040.3890@woody.linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0705172258400.5705@alien.or.mcafeemobile.com>
On Thu, 17 May 2007, Davide Libenzi wrote:
>
> Thx Davi, patch is correct. Nice catch. But at this point instead of
> ending up getting two locks, we may look into using Andrew suggestion of
> reusing the waitqueue lock. Is it universally considered a "legal"
> operation?
Yes. Perhaps not for drivers etc, but stuff that is deeply involved in
waitqueue handling anyway, sure.
Linus
prev parent reply other threads:[~2007-05-18 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 3:45 Davi Arnaut
2007-05-18 6:20 ` Davide Libenzi
2007-05-18 6:37 ` Andrew Morton
2007-05-18 14:45 ` Linus Torvalds [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=alpine.LFD.0.98.0705180744040.3890@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=davi@haxent.com.br \
--cc=davidel@xmailserver.org \
--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
all inboxes | Powered by JetHome®