* [VFS-EXPORTS] Why generic_forget_inode() is not exported?
@ 2004-12-11 13:31 Kirill Korotaev
2004-12-11 15:23 ` Christoph Hellwig
0 siblings, 1 reply; 2+ messages in thread
From: Kirill Korotaev @ 2004-12-11 13:31 UTC (permalink / raw)
To: linux-kernel
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.
Kirill
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [VFS-EXPORTS] Why generic_forget_inode() is not exported?
2004-12-11 13:31 [VFS-EXPORTS] Why generic_forget_inode() is not exported? Kirill Korotaev
@ 2004-12-11 15:23 ` Christoph Hellwig
0 siblings, 0 replies; 2+ messages in thread
From: Christoph Hellwig @ 2004-12-11 15:23 UTC (permalink / raw)
To: Kirill Korotaev; +Cc: linux-kernel
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-12-11 15:23 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-12-11 13:31 [VFS-EXPORTS] Why generic_forget_inode() is not exported? Kirill Korotaev
2004-12-11 15:23 ` Christoph Hellwig
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®