From: Chris Mason <mason@suse.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: Linus Torvalds <torvalds@transmeta.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch 12/16] fix race between writeback and unlink
Date: 03 Jun 2002 18:10:33 -0400 [thread overview]
Message-ID: <1023142233.31475.23.camel@tiny> (raw)
In-Reply-To: <3CF91E48.C76B34FA@zip.com.au>
On Sat, 2002-06-01 at 15:19, Andrew Morton wrote:
> Linus Torvalds wrote:
> >
> > On Sat, 1 Jun 2002, Andrew Morton wrote:
> > >
> > > So run __iget prior to dropping inode_lock.
> >
> > This part looks horrible:
> >
> > + spin_unlock(&inode_lock);
> > + iput(inode);
> > + spin_lock(&inode_lock);
>
> Yup. The inode refcounting APIs are really awkward. Note how I recently
> added dopey code in ext2_put_inode() to only drop the prealloc window on
> the "final" iput().
Hmmm, a quick glance makes the test in ext2_put_inode look unsafe.
iput calls put_inode before decrementing i_count. So, nothing stops 5
iput callers from all deciding i_count > 2 and leaving the preallocation
blocks hanging.
Also, a knfsd triggered iget/iput pair should hit the same race with an
put_inode call.
Or am I missing something?
-chris
next prev parent reply other threads:[~2002-06-03 22:12 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
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 ` Chris Mason [this message]
2002-06-03 22:19 ` [patch 12/16] fix race between writeback and unlink 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=1023142233.31475.23.camel@tiny \
--to=mason@suse.com \
--cc=akpm@zip.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.