From: Christoph Hellwig <hch@infradead.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, esandeen@redhat.com, viro@redhat.com
Subject: Re: [PATCH 3/3] pipefs and sockfs respin -- make .drop_inode = generic_delete_inode
Date: Mon, 22 Jan 2007 20:49:24 +0000 [thread overview]
Message-ID: <20070122204924.GA23297@infradead.org> (raw)
In-Reply-To: <200701221416.l0MEG6le022947@dantu.rdu.redhat.com>
On Mon, Jan 22, 2007 at 09:16:06AM -0500, Jeff Layton wrote:
> A little late since I sent some patches to akpm already, but I'm thinking
> that this might be the better way to go. Rather than trying to have the
> filesystems manage i_nlink, just make drop_inode for the filesystems be
> generic_delete_inode. It seems that some filesystems already do that, and it
> seems like that should do the right thing here too. This seems to be a little
> easier to follow than messing with i_nlink.
>
> Does this seem reasonable? If so, I'll send this on to akpm and ask him to
> commit this rather than the original pipefs patch I sent.
Sounds good to me.
prev parent reply other threads:[~2007-01-22 20:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-22 14:16 [PATCH 3/3] pipefs and sockfs respin -- make .drop_inode = generic_delete_inode Jeff Layton
2007-01-22 20:49 ` 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=20070122204924.GA23297@infradead.org \
--to=hch@infradead.org \
--cc=esandeen@redhat.com \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).