From: Nikita Danilov <Nikita@Namesys.COM>
To: Andrew Morton <akpm@digeo.com>
Cc: Linus Torvalds <Torvalds@Transmeta.COM>,
Linux Kernel Mailing List <Linux-Kernel@vger.kernel.org>
Subject: Re: missed inode->i_hash cleanup in prune_icache()
Date: Fri, 27 Dec 2002 14:41:50 +0300 [thread overview]
Message-ID: <15884.15486.466985.981729@laputa.namesys.com> (raw)
In-Reply-To: <3E0C35DF.2801AA43@digeo.com>
Andrew Morton writes:
> Nikita Danilov wrote:
> >
[...]
> > struct inode *inode;
> >
> > inode = list_entry(head->next, struct inode, i_list);
> > - list_del(&inode->i_list);
> > + list_del_init(&inode->i_list);
> >
> > if (inode->i_data.nrpages)
> > truncate_inode_pages(&inode->i_data, 0);
> >
>
> That's i_list, not i_hash.
>
> Yes, it's a bit sloppy to leave the i_list pointers dangling but
> fs/inode.c:new_inode() will just overwrite i_list and all is well.
>
> Could you please double-check or clarify the need for this change?
You are right, sorry. Probably I stared at these lists for too long or
too short a time. We are seeing garbage on sb->s_io in sync_sb_inodes(),
but probably this is some reiser4 problem after all.
Nikita.
prev parent reply other threads:[~2002-12-27 11:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 10:23 Nikita Danilov
2002-12-27 11:13 ` Andrew Morton
2002-12-27 11:41 ` Nikita Danilov [this message]
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=15884.15486.466985.981729@laputa.namesys.com \
--to=nikita@namesys.com \
--cc=Linux-Kernel@vger.kernel.org \
--cc=Torvalds@Transmeta.COM \
--cc=akpm@digeo.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
all inboxes | Powered by JetHome®