public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Andrew Morton <akpm@zip.com.au>,
	Alexander Viro <aviro@redhat.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] iput() cleanup (was Re: [patch 12/16] fix race between writeback and unlink)
Date: 03 Jun 2002 15:09:36 -0400	[thread overview]
Message-ID: <1023131376.22609.1856.camel@tiny> (raw)
In-Reply-To: <Pine.LNX.4.44.0206022119300.1030-100000@home.transmeta.com>

On Mon, 2002-06-03 at 00:27, Linus Torvalds wrote:
> 
> 
> On Sat, 1 Jun 2002, Andrew Morton wrote:
> >
> > > Why not just split up the code inside iput(), and then just do
> > >
> > >         if (atomic_dec(&inode->i_count))
> > >                 final_iput(inode);
> >
> > Yes, I suspect all the inode refcounting, locking, I_FREEING, I_LOCK, etc
> > could do with a spring clean. Make it a bit more conventional.  I'll
> > discuss with Al when he resurfaces.
> 
> This is a first cut at cleaning up "iput()" and getting rid of some of the
> magic VFS-level behaviour of the i_nlink field which many filesystems do
> not actually want - as shown by the number of "force_delete" users out
> there.
> 
> It does not change any real behaviour, but it splits up the "iput()"
> behaviour into several functions ("common_delete_inode()",
> "common_forget_inode()" and "common_drop_inode()"), and adds a place for a
> low-level filesystem to hook into the behaviour at inode drop time,
> through the "drop_inode" superblock operation.

Now that is kinda neat, calling it with the inode lock held lets me move
some things out of reiserfs_file_release which need i_sem, and move them
into a less expensive drop_inode call without grabbing the semaphore.

-chris



  parent reply	other threads:[~2002-06-03 19:11 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-01  8:43 [patch 12/16] fix race between writeback and unlink Andrew Morton
2002-06-01 16:42 ` Linus Torvalds
2002-06-01 19:19   ` Andrew Morton
2002-06-01 20:04     ` William Lee Irwin III
2002-06-01 22:25       ` Andrew Morton
2002-06-03  4:27     ` [RFC] iput() cleanup (was Re: [patch 12/16] fix race between writeback and unlink) Linus Torvalds
2002-06-03 16:26       ` Andreas Dilger
2002-06-03 16:47         ` Linus Torvalds
2002-06-03 19:09       ` Chris Mason [this message]
2002-06-03 19:34         ` Linus Torvalds
2002-06-03 19:49           ` Chris Mason
2002-06-03 19:55             ` Linus Torvalds
2002-06-03 22:10     ` [patch 12/16] fix race between writeback and unlink Chris Mason
2002-06-03 22:19       ` Linus Torvalds
2002-06-03 22:30         ` Andrew Morton
2002-06-04 18:47           ` Linus Torvalds
2002-06-04 20:15             ` Andrew Morton
2002-06-04 20:23               ` Linus Torvalds
2002-06-04 20:40                 ` Andrew Morton
2002-06-04 21:37                   ` Linus Torvalds
2002-06-04 22:04                     ` Benjamin LaHaise
2002-06-04 22:08                     ` Andrew Morton
2002-07-07 20:38                     ` Riley Williams
2002-06-04 22:05                 ` Craig Milo Rogers
2002-06-04 22:08                   ` Linus Torvalds
2002-06-03 22:36         ` Chris Mason
2002-06-03 22:47           ` 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=1023131376.22609.1856.camel@tiny \
    --to=mason@suse.com \
    --cc=akpm@zip.com.au \
    --cc=aviro@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