linux-kernel - Re: [PATCH 3/3] ensure unique i_ino in filesystems without permanent inode numbers (pipefs)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <457AA9D7.7050509@redhat.com>
Date:	Sat, 09 Dec 2006 07:19:35 -0500
From:	Jeff Layton <jlayton@...hat.com>
To:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 3/3] ensure unique i_ino in filesystems without permanent
 inode numbers (pipefs)

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@...hat.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;

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/