From: Joel Becker <jlbec@evilplan.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org,
Steven Whitehouse <swhiteho@redhat.com>,
Sunil Mushran <sunil.mushran@oracle.com>
Subject: Re: [PATCH] ocfs2: send correct UUID to cleancache initialization
Date: Thu, 17 Nov 2011 01:50:21 -0800 [thread overview]
Message-ID: <20111117095019.GE7319@noexit.corp.google.com> (raw)
In-Reply-To: <dd238ce4-fe92-4dc0-a4b6-7f273c386366@default>
On Mon, Oct 17, 2011 at 04:47:17PM -0700, Dan Magenheimer wrote:
> ocfs2: Fix cleancache initialization call to correctly pass uuid
>
> As reported by Steven Whitehouse in https://lkml.org/lkml/2011/5/27/221
> the ocfs2 volume UUID is incorrectly passed to cleancache.
> As a result, shared-ephemeral tmem pools will not actually
> be created; instead they will be private (unshared) which
> misses out on a major benefit of tmem.
>
> Reported-by: Steven Whitehouse <swhiteho@redhat.com>
> Signed-off-by: Dan Magenheimer <dan.magenheimer@oracle.com>
This patch is now in the 'fixes' branch of ocfs2.git.
Joel
>
> diff --git a/fs/ocfs2/super.c b/fs/ocfs2/super.c
> --- a/fs/ocfs2/super.c
> +++ b/fs/ocfs2/super.c
> @@ -2374,7 +2374,7 @@ static int ocfs2_initialize_super(struct super_block *sb,
> mlog_errno(status);
> goto bail;
> }
> - cleancache_init_shared_fs((char *)&uuid_net_key, sb);
> + cleancache_init_shared_fs((char *)&di->id2.i_super.s_uuid, sb);
>
> bail:
> return status;
--
"Well-timed silence hath more eloquence than speech."
- Martin Fraquhar Tupper
http://www.jlbec.org/
jlbec@evilplan.org
prev parent reply other threads:[~2011-11-17 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 23:47 Dan Magenheimer
2011-11-17 9:50 ` Joel Becker [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=20111117095019.GE7319@noexit.corp.google.com \
--to=jlbec@evilplan.org \
--cc=dan.magenheimer@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=sunil.mushran@oracle.com \
--cc=swhiteho@redhat.com \
/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
Powered by JetHome