public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin LaHaise <bcrl@redhat.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] 2.5.22 add __fput for aio
Date: Mon, 17 Jun 2002 16:19:31 -0400	[thread overview]
Message-ID: <20020617161931.E1457@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0206171307180.2949-100000@home.transmeta.com>; from torvalds@transmeta.com on Mon, Jun 17, 2002 at 01:11:04PM -0700

On Mon, Jun 17, 2002 at 01:11:04PM -0700, Linus Torvalds wrote:
> The other alternative is that aio only does the book-keeping from
> interrupt context, adds the "struct file * to be freed" to some list of
> freeable files, and then does __fput() from _non_interrupt_ context on
> those files.
> 
> Is that was aio actually _does_?

Yes -- aio does the atomic_dec_and_test in the interrupt handler, and 
if that was the last user of the struct file *, it queues the io handle 
for cleanup from task context.

> If so, the code may be fine, but the comments are misleading crap and
> should be fixed asap.

Sure.  How's changing it to: 

+/* __fput is called from task task when aio completion releases the last
+ * use of a struct file *.  Do not use otherwise.
+ */

instead?

		-ben
-- 
"You will be reincarnated as a toad; and you will be much happier."

  reply	other threads:[~2002-06-17 20:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-17 19:47 [patch] 2.5.22 add __fput for aio Benjamin LaHaise
2002-06-17 20:11 ` Linus Torvalds
2002-06-17 20:19   ` Benjamin LaHaise [this message]
2002-06-17 20:22     ` Linus Torvalds
2002-06-17 20:41       ` Dynamic Timer X.Xiao
2002-06-17 22:27         ` george anzinger

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=20020617161931.E1457@redhat.com \
    --to=bcrl@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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