From: Andrea Arcangeli <andrea@novell.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@suse.de>,
Christoph Rohland <cr@sap.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tmpfs symlink corrupts mempolicy
Date: Tue, 16 Nov 2004 03:14:05 +0100 [thread overview]
Message-ID: <20041116021405.GJ4758@dualathlon.random> (raw)
In-Reply-To: <Pine.LNX.4.44.0411160008500.2835-100000@localhost.localdomain>
On Tue, Nov 16, 2004 at 12:26:05AM +0000, Hugh Dickins wrote:
> On Mon, 15 Nov 2004, Andrea Arcangeli wrote:
> >
> > this patch is completely broken, delete_inode isn't going to be called
> > when the inode is being shrunk. delete_inode is only good for truncate,
>
> Do you mean "when the inode cache is being shrunk"?
> By "truncate" there you mean "unlink"?
yes.
> > this patch will tend to work until the vm shrink the dcache, then it'll
> > crash, sorry.
>
> Sorry, you can see I'm having some trouble understanding your reply.
>
> I think you're forgetting that tmpfs inodes live nowhere but in memory:
> if shrinking the inode cache were to remove tmpfs inodes, it would be a
> considerably more temporary fs than could ever be useful. There's an
> extra dget that keeps dentry and inode safe from pruning.
I was wrong about it crashing, but it will not crash only for shmfs,
if you want to export that to MAP_SHARED on other fs, you won't be
allowed anymore to depending on this shmfs speciaility of delete_inode
being recalled only during unlink. I don't see how depending on this
subtle detail to free the mpol could ever be an improvement instead of
doing in destroy_inode where it belongs to.
next prev parent reply other threads:[~2004-11-16 2:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 20:41 [PATCH] tmpfs symlink corrupts mempolicy Hugh Dickins
2004-11-15 22:34 ` Andrea Arcangeli
2004-11-16 0:26 ` Hugh Dickins
2004-11-16 2:14 ` Andrea Arcangeli [this message]
2004-11-16 5:50 ` Hugh Dickins
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=20041116021405.GJ4758@dualathlon.random \
--to=andrea@novell.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=cr@sap.com \
--cc=hugh@veritas.com \
--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