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@kernel.dk,
	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 -V21 12/12] ext4: Copy fs UUID to superblock
Date: Tue,  5 Oct 2010 15:52:20 +0530	[thread overview]
Message-ID: <1286274140-26533-13-git-send-email-aneesh.kumar@linux.vnet.ibm.com> (raw)
In-Reply-To: <1286274140-26533-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>

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

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 2614774..b46a78c 100644
--- a/fs/ext4/super.c
+++ b/fs/ext4/super.c
@@ -2941,6 +2941,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.0.4

  parent reply	other threads:[~2010-10-05 10:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05 10:22 [PATCH -V21 00/12] Generic name to handle and open by handle syscalls Aneesh Kumar K.V
2010-10-05 10:22 ` [PATCH -V21 01/12] exportfs: Return the minimum required handle size Aneesh Kumar K.V
2010-10-05 10:22 ` [PATCH -V21 02/12] vfs: Add name to file handle conversion support Aneesh Kumar K.V
2010-10-05 10:22 ` [PATCH -V21 03/12] vfs: Add open by file handle support Aneesh Kumar K.V
2010-10-05 10:22 ` [PATCH -V21 04/12] vfs: Add handle based readlink syscall Aneesh Kumar K.V
2010-10-05 10:22 ` [PATCH -V21 05/12] vfs: Add handle based stat syscall Aneesh Kumar K.V
2010-10-05 10:22 ` [PATCH -V21 06/12] vfs: Add handle based link syscall Aneesh Kumar K.V
2010-10-05 10:22 ` [PATCH -V21 07/12] x86: Add new syscalls for x86_32 Aneesh Kumar K.V
2010-10-05 10:22 ` [PATCH -V21 08/12] x86: Add new syscalls for x86_64 Aneesh Kumar K.V
2010-10-05 10:22 ` [PATCH -V21 09/12] unistd.h: Add new syscalls numbers to asm-generic Aneesh Kumar K.V
2010-10-05 10:22 ` [PATCH -V21 10/12] vfs: Export file system uuid via /proc/<pid>/mountinfo Aneesh Kumar K.V
2010-10-05 10:22 ` [PATCH -V21 11/12] ext3: Copy fs UUID to superblock Aneesh Kumar K.V
2010-10-05 10:22 ` Aneesh Kumar K.V [this message]
2010-10-11 23:34 ` [PATCH -V21 00/12] Generic name to handle and open by handle syscalls J. Bruce Fields
2010-10-24 15:03 ` Aneesh Kumar K. V

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=1286274140-26533-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@kernel.dk \
    --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).