From: Andrew Morton <akpm@osdl.org>
To: Kirill Korotaev <dev@sw.ru>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: Q: bugs in generic_forget_inode()?
Date: Mon, 6 Sep 2004 12:35:34 -0700 [thread overview]
Message-ID: <20040906123534.3487839e.akpm@osdl.org> (raw)
In-Reply-To: <413C52E2.10809@sw.ru>
Kirill Korotaev <dev@sw.ru> wrote:
>
> Hello,
>
> 1. I found that generic_forget_inode() calls write_inode_now() dropping
> inode_lock and destroys inode after that. The problem is that
> write_inode_now() can sleep and during this sleep someone can find inode
> in the hash, w/o I_FREEING state and with i_count = 0.
The filesystem is in the process of being unmounted (!MS_ACTIVE). So the
question is: who is doing inode lookups against a soon-to-be-defunct
filesystem?
next prev parent reply other threads:[~2004-09-06 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-06 12:06 Kirill Korotaev
2004-09-06 19:35 ` Andrew Morton [this message]
2004-09-10 9:04 ` Kirill Korotaev
2004-09-10 9:11 ` 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=20040906123534.3487839e.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dev@sw.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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
Powered by JetHome