public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@redhat.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 3/3] ensure unique i_ino in filesystems without permanent inode numbers (pipefs)
Date: Sat, 09 Dec 2006 07:19:35 -0500	[thread overview]
Message-ID: <457AA9D7.7050509@redhat.com> (raw)
In-Reply-To: <457891F8.9090607@redhat.com>

Jeff Layton wrote:
 > pipefs is a rather busy filesystem and so is a good place to start to make
 > sure we flush out any performance problems
 >

This patch changes the earlier patch to use the new_registered_inode wrapper
and that simplifies things a bit. It also goes ahead and changes over sockfs
in the same way.

Signed-off-by: Jeff Layton <jlayton@redhat.com>

diff --git a/fs/pipe.c b/fs/pipe.c
index f8b6bdc..4d30f49 100644
--- a/fs/pipe.c
+++ b/fs/pipe.c
@@ -846,7 +846,7 @@ static struct dentry_operations pipefs_d

  static struct inode * get_pipe_inode(void)
  {
-	struct inode *inode = new_inode(pipe_mnt->mnt_sb);
+	struct inode *inode = new_registered_inode(pipe_mnt->mnt_sb, 0);
  	struct pipe_inode_info *pipe;

  	if (!inode)
diff --git a/net/socket.c b/net/socket.c
index 4e39631..ec63a96 100644
--- a/net/socket.c
+++ b/net/socket.c
@@ -486,7 +486,7 @@ static struct socket *sock_alloc(void)
  	struct inode *inode;
  	struct socket *sock;

-	inode = new_inode(sock_mnt->mnt_sb);
+	inode = new_registered_inode(sock_mnt->mnt_sb, 0);
  	if (!inode)
  		return NULL;


      reply	other threads:[~2006-12-09 12:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07 22:13 [PATCH 3/3] ensure unique i_ino in filesystems without permanent inode numbers (pipefs) Jeff Layton
2006-12-09 12:19 ` Jeff Layton [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=457AA9D7.7050509@redhat.com \
    --to=jlayton@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --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