From: Christoph Rohland <cr@sap.com>
To: Cristiano Paris <c.paris@libero.it>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: ramfs and inode
Date: 16 Nov 2001 14:25:29 +0100 [thread overview]
Message-ID: <m3adxmlueu.fsf@linux.local> (raw)
In-Reply-To: <Pine.LNX.4.33.0111151746490.405-100000@lisa.rhpk.springfield.inwind.it>
In-Reply-To: <Pine.LNX.4.33.0111151746490.405-100000@lisa.rhpk.springfield.inwind.it>
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
prev parent reply other threads:[~2001-11-16 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-15 16:48 ramfs and inode Cristiano Paris
2001-11-16 13:25 ` Christoph Rohland [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=m3adxmlueu.fsf@linux.local \
--to=cr@sap.com \
--cc=c.paris@libero.it \
--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