linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: hch@infradead.org, viro@zeniv.linux.org.uk, adilger@sun.com,
	corbet@lwn.net, neilb@suse.de, npiggin@suse.de,
	hooanon05@yahoo.co.jp, bfields@fieldses.org, miklos@szeredi.hu
Cc: linux-fsdevel@vger.kernel.org, sfrench@us.ibm.com,
	philippe.deniel@CEA.FR, linux-kernel@vger.kernel.org,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: [PATCH -V17 12/12] ext4: Copy fs UUID to superblock
Date: Tue, 20 Jul 2010 00:42:07 +0530	[thread overview]
Message-ID: <1279566727-16598-13-git-send-email-aneesh.kumar@linux.vnet.ibm.com> (raw)
In-Reply-To: <1279566727-16598-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>

File system UUID is made available to application
via  /proc/<pid>/mountinfo

Acked-by: Serge Hallyn <serue@us.ibm.com>
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
---
 fs/ext4/super.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/fs/ext4/super.c b/fs/ext4/super.c
index 4e8983a..f2bd1bc 100644
--- a/fs/ext4/super.c
+++ b/fs/ext4/super.c
@@ -2816,6 +2816,8 @@ static int ext4_fill_super(struct super_block *sb, void *data, int silent)
 	sb->s_qcop = &ext4_qctl_operations;
 	sb->dq_op = &ext4_quota_operations;
 #endif
+	memcpy(sb->s_uuid, es->s_uuid, sizeof(es->s_uuid));
+
 	INIT_LIST_HEAD(&sbi->s_orphan); /* unlinked but open files */
 	mutex_init(&sbi->s_orphan_lock);
 	mutex_init(&sbi->s_resize_lock);
-- 
1.7.2.rc3.43.g24e7a


      parent reply	other threads:[~2010-07-19 19:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-19 19:11 [PATCH -V17 0/12] Generic name to handle and open by handle syscalls Aneesh Kumar K.V
2010-07-19 19:11 ` [PATCH -V17 01/12] exportfs: Return the minimum required handle size Aneesh Kumar K.V
2010-07-19 19:11 ` [PATCH -V17 02/12] vfs: Add name to file handle conversion support Aneesh Kumar K.V
2010-07-19 19:11 ` [PATCH -V17 03/12] vfs: Add open by file handle support Aneesh Kumar K.V
2010-07-19 19:11 ` [PATCH -V17 04/12] vfs: Allow handle based open on symlinks Aneesh Kumar K.V
2010-07-19 19:12 ` [PATCH -V17 05/12] vfs: Support null pathname in readlink Aneesh Kumar K.V
2010-07-19 19:12 ` [PATCH -V17 06/12] vfs: Support null pathname in faccessat Aneesh Kumar K.V
2010-07-19 19:12 ` [PATCH -V17 07/12] vfs: Support null pathname in linkat Aneesh Kumar K.V
2010-07-19 19:12 ` [PATCH -V17 08/12] x86: Add new syscalls for x86_32 Aneesh Kumar K.V
2010-07-19 19:12 ` [PATCH -V17 09/12] x86: Add new syscalls for x86_64 Aneesh Kumar K.V
2010-07-19 19:12 ` [PATCH -V17 10/12] vfs: Export file system uuid via /proc/<pid>mountinfo Aneesh Kumar K.V
2010-08-08 16:04   ` Ted Ts'o
2010-08-09 14:54     ` Aneesh Kumar K. V
2010-07-19 19:12 ` [PATCH -V17 11/12] ext3: Copy fs UUID to superblock Aneesh Kumar K.V
2010-07-19 19:12 ` Aneesh Kumar K.V [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=1279566727-16598-13-git-send-email-aneesh.kumar@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=adilger@sun.com \
    --cc=bfields@fieldses.org \
    --cc=corbet@lwn.net \
    --cc=hch@infradead.org \
    --cc=hooanon05@yahoo.co.jp \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=neilb@suse.de \
    --cc=npiggin@suse.de \
    --cc=philippe.deniel@CEA.FR \
    --cc=sfrench@us.ibm.com \
    --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 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).