From: Christoph Hellwig <hch@infradead.org>
To: Kirill Korotaev <dev@sw.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [VFS-EXPORTS] Why generic_forget_inode() is not exported?
Date: Sat, 11 Dec 2004 15:23:39 +0000 [thread overview]
Message-ID: <20041211152339.GA11522@infradead.org> (raw)
In-Reply-To: <41BAF6A7.6070102@sw.ru>
On Sat, Dec 11, 2004 at 04:31:19PM +0300, Kirill Korotaev wrote:
> Hello,
>
> I have a question about EXPORTS in VEFS:
> if sb->drop_inode method is set, than it's called in iput_final().
> But it's impossible to call neither generic_drop_inode(), nor
> generic_forget_inode() inside this handler. Only generic_delete_inode()
> is accessiable.
>
> why generic_delete_inode() is exported and generic_forget_inode() is not?
> It looks like it should. At least, from VFS interface point of view.
Because a) there's no intree user and b) people haven't explained why
they need it.
prev parent reply other threads:[~2004-12-11 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-11 13:31 Kirill Korotaev
2004-12-11 15:23 ` Christoph Hellwig [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=20041211152339.GA11522@infradead.org \
--to=hch@infradead.org \
--cc=dev@sw.ru \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®