From: Andi Kleen <andi@firstfloor.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Christoph Hellwig <hch@infradead.org>,
corbet@lwn.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [2/11] Add unlocked_fasync
Date: Mon, 19 May 2008 17:45:35 +0200 [thread overview]
Message-ID: <4831A09F.8090300@firstfloor.org> (raw)
In-Reply-To: <20080519162206.18949d0b@core>
Alan Cox wrote:
>> The good news is that none of them I looked at actually needed BKL
>> (or perhaps I just missed it)
>
> Far better to send an initial patch that simply adds all the lock/unlocks
> then remove them later than worry about it immediately - that makes it
> easier to verify changes and to do testing
I fail to see how that makes it easier than with ->fasync_unlocked.
-Andi
next prev parent reply other threads:[~2008-05-19 15:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 12:31 [PATCH] [0/11] Repost of old VFS BKL patchkit Andi Kleen
2008-05-19 12:31 ` [PATCH] [1/11] Remove BKL from remote_llseek Andi Kleen
2008-05-19 13:58 ` Trond Myklebust
2008-05-19 14:41 ` Andi Kleen
2008-05-19 14:02 ` Christoph Hellwig
2008-05-19 15:13 ` Andi Kleen
2008-05-19 16:09 ` Steve French
2008-05-19 12:31 ` [PATCH] [2/11] Add unlocked_fasync Andi Kleen
2008-05-19 14:03 ` Christoph Hellwig
2008-05-19 14:43 ` Andi Kleen
2008-05-19 15:12 ` Alan Cox
2008-05-19 15:29 ` Andi Kleen
2008-05-19 15:22 ` Alan Cox
2008-05-19 15:45 ` Andi Kleen [this message]
2008-05-19 17:29 ` Randy Dunlap
2008-05-19 12:31 ` [PATCH] [3/11] Convert pipe over to unlocked_fasync Andi Kleen
2008-05-19 12:31 ` [PATCH] [4/11] Convert socket fasync " Andi Kleen
2008-05-19 12:31 ` [PATCH] [5/11] Convert fuse " Andi Kleen
2008-05-19 12:31 ` [PATCH] [6/11] Convert bad_inode " Andi Kleen
2008-05-19 12:31 ` [PATCH] [7/11] Convert DRM " Andi Kleen
2008-05-19 12:31 ` [PATCH] [8/11] Use unlocked_fasync in random.c Andi Kleen
2008-05-19 12:31 ` [PATCH] [9/11] Convert hpet to unlocked_fasync Andi Kleen
2008-05-19 12:31 ` [PATCH] [10/11] Use unlocked_fasync in RTC Andi Kleen
2008-05-19 12:31 ` [PATCH] [11/11] Convert uio to fasync_unlocked Andi Kleen
2008-05-19 12:48 ` Andi Kleen
2008-05-19 13:30 ` Hans J. Koch
-- strict thread matches above, loose matches on Subject: below --
2008-05-20 15:28 [PATCH] [0/11] REPOST: Early exception fixes Andi Kleen
2008-05-20 15:28 ` [PATCH] [2/11] Add unlocked_fasync Andi Kleen
2008-05-20 15:58 ` Arjan van de Ven
2008-05-20 18:30 ` Andi Kleen
2008-05-20 20:06 ` Arjan van de Ven
2008-05-20 23:35 ` Andi Kleen
2008-05-21 4:47 ` Arjan van de Ven
2008-05-20 18:33 ` Alan Cox
2008-05-20 18:59 ` Andi Kleen
2008-05-20 15:58 ` Randy Dunlap
2008-05-20 15:58 ` Jonathan Corbet
2008-05-20 18:31 ` Andi Kleen
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=4831A09F.8090300@firstfloor.org \
--to=andi@firstfloor.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=corbet@lwn.net \
--cc=hch@infradead.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