[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <485BEEF7.2020404@firstfloor.org>
Date: Fri, 20 Jun 2008 19:55:03 +0200
From: Andi Kleen <andi@...stfloor.org>
To: Jonathan Corbet <corbet@....net>
CC: LKML <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Al Viro <viro@...IV.linux.org.uk>
Subject: Re: [PATCH, RFC] fasync() BKL pushdown
Jonathan Corbet wrote:
> The majority of fasync() functions just call fasync_helper() with a pointer
> to an fasync_struct reachable from the file structure. Given that (1) the
> struct file will not go away while fasync() is running, and (2) the
> VFS-level fasync() stuff is protected with the Big Fasync Lock, I contend
> that these simple implementations have no need for the BKL.
Not necessarily true, they might require BKL still for fd live time issues.
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists