public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Andi Kleen <andi@firstfloor.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, andi@firstfloor.org,
	viro@ZenIV.linux.org.uk, oleg@redhat.com,
	linux-api@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH, RFC] Remove fasync() BKL usage, take 3325
Date: Thu, 22 Jan 2009 23:01:45 -0700	[thread overview]
Message-ID: <20090122230145.7e434dee@tpl> (raw)
In-Reply-To: <20090123055404.GL15750@one.firstfloor.org>

On Fri, 23 Jan 2009 06:54:04 +0100
Andi Kleen <andi@firstfloor.org> wrote:

> The state needs to be protected while the per driver ->fasync callback
> runs, otherwise the bit can get out of sync with what the driver
> thinks it is.
> 
> Mind you imho the best way would be to move the bit manipulation for
> that into the drivers, but that would require to change them all.

You know, I'm not sure why I didn't look into that.  Do we want drivers
reaching directly into struct file and making changes?  Maybe a helper
would be better.  Hmm, maybe we could call it fasync_helper() and it
could just do the right thing?  Will investigate further...

jon

  reply	other threads:[~2009-01-23  6:02 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-15 22:32 [PATCH, RFC] Remove fasync() BKL usage, take 3325 Jonathan Corbet
2009-01-22 14:51 ` Andrew Morton
2009-01-22 16:09   ` Andi Kleen
2009-01-23  5:21     ` Jonathan Corbet
2009-01-22 20:32   ` Christoph Hellwig
2009-01-23  4:56     ` Andi Kleen
2009-01-28  0:53       ` Andrew Morton
2009-01-28  0:55       ` Andrew Morton
2009-01-28  3:14         ` Oleg Nesterov
2009-01-28  3:57           ` Jonathan Corbet
2009-01-28  4:23             ` Oleg Nesterov
2009-01-28 14:13               ` Jonathan Corbet
2009-01-28 17:36           ` Christoph Hellwig
2009-01-28 17:44             ` Jonathan Corbet
2009-01-28 17:55               ` Christoph Hellwig
2009-01-28 18:13                 ` Matt Mackall
2009-01-28 21:05                   ` Jonathan Corbet
2009-01-28 18:14             ` David Daney
2009-01-29 14:37             ` Andi Kleen
2009-01-23  5:15   ` Jonathan Corbet
2009-01-23  5:31     ` Andrew Morton
2009-01-23  5:45       ` Matt Mackall
2009-01-23  6:15         ` Andi Kleen
2009-01-23 10:45           ` Bernd Petrovitsch
2009-01-23  5:54       ` Andi Kleen
2009-01-23  6:01         ` Jonathan Corbet [this message]
2009-01-23  6:57         ` Andrew Morton

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=20090122230145.7e434dee@tpl \
    --to=corbet@lwn.net \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andi@firstfloor.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --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