From: hooanon05g@gmail.com
To: linux-fsdevel@vger.kernel.org, adilger@dilger.ca, hch@lst.de,
dchinner@redhat.com, viro@zeniv.linux.org.uk
Cc: jlbec@evilplan.org, gregkh@linuxfoundation.org, hughd@google.com
Subject: [RFC 3/3] uniqueness of inode number, configfs, debugfs, procfs, ramfs and tmpfs
Date: Thu, 22 May 2014 03:49:00 +0900 [thread overview]
Message-ID: <1400698140-25853-4-git-send-email-hooanon05g@gmail.com> (raw)
In-Reply-To: <1400698140-25853-1-git-send-email-hooanon05g@gmail.com>
From: "J. R. Okajima" <hooanon05g@gmail.com>
Turn the feature ON which was introduced by previous commit.
Signed-off-by: J. R. Okajima <hooanon05g@gmail.com>
---
fs/configfs/inode.c | 2 +-
fs/debugfs/inode.c | 2 +-
fs/proc/base.c | 2 +-
fs/proc/proc_sysctl.c | 2 +-
fs/ramfs/inode.c | 2 +-
mm/shmem.c | 2 +-
6 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/fs/configfs/inode.c b/fs/configfs/inode.c
index 06034b3..e58413a 100644
--- a/fs/configfs/inode.c
+++ b/fs/configfs/inode.c
@@ -135,7 +135,7 @@ struct inode *configfs_new_inode(umode_t mode, struct configfs_dirent *sd,
{
struct inode * inode = new_inode(s);
if (inode) {
- inode->i_ino = get_next_ino(NULL);
+ inode->i_ino = get_next_ino(s);
inode->i_mapping->a_ops = &configfs_aops;
inode->i_mapping->backing_dev_info = &configfs_backing_dev_info;
inode->i_op = &configfs_inode_operations;
diff --git a/fs/debugfs/inode.c b/fs/debugfs/inode.c
index d29eeb8..c0a1986 100644
--- a/fs/debugfs/inode.c
+++ b/fs/debugfs/inode.c
@@ -41,7 +41,7 @@ static struct inode *debugfs_get_inode(struct super_block *sb, umode_t mode, dev
struct inode *inode = new_inode(sb);
if (inode) {
- inode->i_ino = get_next_ino(NULL);
+ inode->i_ino = get_next_ino(sb);
inode->i_mode = mode;
inode->i_atime = inode->i_mtime = inode->i_ctime = CURRENT_TIME;
switch (mode & S_IFMT) {
diff --git a/fs/proc/base.c b/fs/proc/base.c
index d43b2be..9929c35 100644
--- a/fs/proc/base.c
+++ b/fs/proc/base.c
@@ -1518,7 +1518,7 @@ struct inode *proc_pid_make_inode(struct super_block * sb, struct task_struct *t
/* Common stuff */
ei = PROC_I(inode);
- inode->i_ino = get_next_ino(NULL);
+ inode->i_ino = get_next_ino(sb);
inode->i_mtime = inode->i_atime = inode->i_ctime = CURRENT_TIME;
inode->i_op = &proc_def_inode_operations;
diff --git a/fs/proc/proc_sysctl.c b/fs/proc/proc_sysctl.c
index 7457bde..2d27e24 100644
--- a/fs/proc/proc_sysctl.c
+++ b/fs/proc/proc_sysctl.c
@@ -402,7 +402,7 @@ static struct inode *proc_sys_make_inode(struct super_block *sb,
if (!inode)
goto out;
- inode->i_ino = get_next_ino(NULL);
+ inode->i_ino = get_next_ino(sb);
sysctl_head_get(head);
ei = PROC_I(inode);
diff --git a/fs/ramfs/inode.c b/fs/ramfs/inode.c
index 0eff96e..eef0528 100644
--- a/fs/ramfs/inode.c
+++ b/fs/ramfs/inode.c
@@ -64,7 +64,7 @@ struct inode *ramfs_get_inode(struct super_block *sb,
struct inode * inode = new_inode(sb);
if (inode) {
- inode->i_ino = get_next_ino(NULL);
+ inode->i_ino = get_next_ino(sb);
inode_init_owner(inode, dir, mode);
inode->i_mapping->a_ops = &ramfs_aops;
inode->i_mapping->backing_dev_info = &ramfs_backing_dev_info;
diff --git a/mm/shmem.c b/mm/shmem.c
index 7dc9f19..56a7f94 100644
--- a/mm/shmem.c
+++ b/mm/shmem.c
@@ -1306,7 +1306,7 @@ static struct inode *shmem_get_inode(struct super_block *sb, const struct inode
inode = new_inode(sb);
if (inode) {
- inode->i_ino = get_next_ino(NULL);
+ inode->i_ino = get_next_ino(sb);
inode_init_owner(inode, dir, mode);
inode->i_blocks = 0;
inode->i_mapping->backing_dev_info = &shmem_backing_dev_info;
--
1.7.10.4
next prev parent reply other threads:[~2014-05-21 18:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 18:48 [RFC 0/3] vfs: get_next_ino(), never inum=0 and uniqueness hooanon05g
2014-05-21 18:48 ` [RFC 1/3] vfs: get_next_ino(), never inum=0 hooanon05g
2014-05-28 4:28 ` Hugh Dickins
2014-05-28 5:53 ` Eric Dumazet
2014-05-21 18:48 ` [RFC 2/3] vfs: get_next_ino(), support for the uniqueness hooanon05g
2014-05-22 11:56 ` Jan Kara
2014-05-22 15:03 ` J. R. Okajima
2014-05-22 15:12 ` Jan Kara
2014-05-22 15:14 ` Christoph Hellwig
2014-05-22 16:06 ` Jan Kara
2014-05-29 15:46 ` [PATCH v2 1/2] tmpfs: manage the inode-number by IDR J. R. Okajima
2014-05-29 15:46 ` [PATCH v2 2/2] tmpfs: refine a file handle for NFS-exporting J. R. Okajima
2014-05-31 2:43 ` [PATCH v2 1/2] tmpfs: manage the inode-number by IDR J. R. Okajima
2014-06-01 16:18 ` [RFC PATCH v3 0/2] the uniquness of tmpfs inode-number J. R. Okajima
2014-06-01 16:18 ` [RFC PATCH v3 1/2] tmpfs: manage the inode-number by IDR, signed int inum J. R. Okajima
2014-06-03 9:04 ` Jan Kara
2014-06-03 14:36 ` J. R. Okajima
2014-06-05 12:27 ` [RFC PATCH v4 0/2] tmpfs: manage the inode-number by IDR (performance measure) J. R. Okajima
2014-06-05 12:27 ` [RFC PATCH v4 1/2] tmpfs: manage the inode-number by IDR, signed int inum J. R. Okajima
2014-06-05 12:27 ` [RFC PATCH v4 2/2] tmpfs: refine a file handle for NFS-exporting J. R. Okajima
2014-06-01 16:18 ` [RFC PATCH v3 " J. R. Okajima
2014-05-21 18:49 ` hooanon05g [this message]
2014-05-22 1:03 ` [RFC 3/3] uniqueness of inode number, configfs, debugfs, procfs, ramfs and tmpfs J. R. Okajima
2014-05-22 11:53 ` Jan Kara
2014-05-22 14:58 ` J. R. Okajima
2014-05-22 15:09 ` Jan Kara
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=1400698140-25853-4-git-send-email-hooanon05g@gmail.com \
--to=hooanon05g@gmail.com \
--cc=adilger@dilger.ca \
--cc=dchinner@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=hughd@google.com \
--cc=jlbec@evilplan.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.