From: Andrea Arcangeli <andrea@suse.de>
To: Alexander Viro <viro@math.psu.edu>
Cc: Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: 2.4.15-pre9 breakage (inode.c)
Date: Sat, 24 Nov 2001 07:26:36 +0100 [thread overview]
Message-ID: <20011124072636.B2398@athlon.random> (raw)
In-Reply-To: <Pine.LNX.4.33.0111232154320.1821-100000@penguin.transmeta.com> <Pine.GSO.4.21.0111240105100.4000-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0111240105100.4000-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Sat, Nov 24, 2001 at 01:08:49AM -0500
On Sat, Nov 24, 2001 at 01:08:49AM -0500, Alexander Viro wrote:
>
>
> On Fri, 23 Nov 2001, Linus Torvalds wrote:
>
> > > - if (!list_empty(&inode->i_hash) && sb && sb->s_root) {
> > > + if (!list_empty(&inode->i_hash)) {
> > > if (!(inode->i_state & (I_DIRTY|I_LOCK))) {
> > > list_del(&inode->i_list);
> > > list_add(&inode->i_list, &inode_unused);
> >
> > I have to say that I like this patch better myself - the added tests are
> > not sensible, and just removing them seems to be the right thing.
>
> Test for ->s_root is bogus and had been removed - check the patch I've sent.
>
> However, that variant suffers from the following problem: if ->read_super()
> fails after it had done _any_ iget() (root inode, journal, whatever) -
> we are screwed. Sure, we do iput(). And then we have inode stuck in icache,
you are screwed because you were running a broken filesystem: it is its
own business to drop the inodes if it fails, all it needs to do is to
call invalidate_inodes(s) internally before returning from the read_super
in the failure case.
> with ->i_sb pointing nowhere. When it finally gets evicted we call
> inode->i_sb->s_op->clear_inode(). Oops...
Andrea
next prev parent reply other threads:[~2001-11-24 6:26 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-23 21:22 2.4.15-pre9 breakage (inode.c) Alexander Viro
2001-11-23 21:42 ` Jeff Merkey
2001-11-23 21:51 ` [PATCH][CFT] " Alexander Viro
2001-11-23 22:06 ` Alexander Viro
2001-11-23 22:34 ` Russell King
2001-11-23 22:35 ` Phil Sorber
2001-11-23 22:49 ` Alexander Viro
2001-11-23 23:05 ` Andreas Dilger
2001-11-23 23:35 ` Russell King
2001-11-24 1:48 ` Linus Torvalds
2001-11-24 5:47 ` Andrea Arcangeli
2001-11-24 5:55 ` Linus Torvalds
2001-11-24 6:08 ` Alexander Viro
2001-11-24 6:26 ` Andrea Arcangeli [this message]
2001-11-24 6:31 ` Alexander Viro
2001-11-24 6:37 ` Alexander Viro
2001-11-24 6:50 ` Andrea Arcangeli
2001-11-24 6:58 ` Alexander Viro
2001-11-24 7:01 ` Andrea Arcangeli
2001-11-24 7:06 ` Alexander Viro
2001-11-24 7:12 ` Andrea Arcangeli
2001-11-24 7:30 ` Alexander Viro
2001-11-24 7:44 ` Andrea Arcangeli
2001-11-24 8:05 ` Alexander Viro
2001-11-24 8:21 ` Andrea Arcangeli
2001-11-24 8:38 ` Alexander Viro
2001-11-24 9:38 ` Andrea Arcangeli
2001-11-24 9:56 ` Alexander Viro
2001-11-24 10:25 ` Andrea Arcangeli
2001-11-24 6:44 ` Andrea Arcangeli
2001-11-24 6:51 ` Alexander Viro
2001-11-24 9:00 ` Russell King
2001-11-24 10:20 ` Christian Bornträger
2001-11-24 6:04 ` Alexander Viro
2001-11-24 6:20 ` Andrea Arcangeli
2001-11-24 6:29 ` Alexander Viro
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=20011124072636.B2398@athlon.random \
--to=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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.