* ramfs and inode
@ 2001-11-15 16:48 Cristiano Paris
2001-11-16 13:25 ` Christoph Rohland
0 siblings, 1 reply; 2+ messages in thread
From: Cristiano Paris @ 2001-11-15 16:48 UTC (permalink / raw)
To: linux-kernel
I need an explanation, if possible.
I'm pretty sure that a VFS' inode which refers to a ramfs' file is never
released (i.e. deleted) until that is unlinked. Anyway, I cannot find a
formal verification of this assertion.
Can you help ?
Cristiano
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: ramfs and inode
2001-11-15 16:48 ramfs and inode Cristiano Paris
@ 2001-11-16 13:25 ` Christoph Rohland
0 siblings, 0 replies; 2+ messages in thread
From: Christoph Rohland @ 2001-11-16 13:25 UTC (permalink / raw)
To: Cristiano Paris; +Cc: linux-kernel
Hi Cristiano,
On Thu, 15 Nov 2001, Cristiano Paris wrote:
> I need an explanation, if possible.
>
> I'm pretty sure that a VFS' inode which refers to a ramfs' file is
> never released (i.e. deleted) until that is unlinked. Anyway, I
> cannot find a formal verification of this assertion.
Yes, that's the way it is designed. The struct inode _is_ the ramfs
inode. If you delete the inode, the content is gone...
Greetings
Christoph
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-11-16 13:26 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-11-15 16:48 ramfs and inode Cristiano Paris
2001-11-16 13:25 ` Christoph Rohland
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox