From: "J. Bruce Fields" <bfields@fieldses.org>
To: ycnian@gmail.com
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] nfs: fix wrong object type in lockowner_slab
Date: Wed, 24 Oct 2012 15:42:24 -0400 [thread overview]
Message-ID: <20121024194224.GB6697@fieldses.org> (raw)
In-Reply-To: <1351061059-29318-1-git-send-email-ycnian@gmail.com>
On Wed, Oct 24, 2012 at 02:44:19PM +0800, ycnian@gmail.com wrote:
> From: Yanchuan Nian <ycnian@gmail.com>
>
> The object type in the cache of lockowner_slab is wrong, and it is better to fix it.
>
> Signed-off-by: Yanchuan Nian <ycnian@gmail.com>
> ---
> fs/nfsd/nfs4state.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> index cc894ed..1609eb2 100644
> --- a/fs/nfsd/nfs4state.c
> +++ b/fs/nfsd/nfs4state.c
> @@ -2325,7 +2325,7 @@ nfsd4_init_slabs(void)
> if (openowner_slab == NULL)
> goto out_nomem;
> lockowner_slab = kmem_cache_create("nfsd4_lockowners",
> - sizeof(struct nfs4_openowner), 0, 0, NULL);
> + sizeof(struct nfs4_lockowner), 0, 0, NULL);
Thanks!
The first three fields of each are the same, the rest is:
struct nfs4_openowner {
...
pointer
time_t
unsigned char
}
struct nfs4_lockowner {
...
struct list_head
}
Is it always true that
sizeof(struct nfs4_openowner) >= sizeof9struct nfs4_lockowner)
? I think so, in which case this isn't urgent.... Applying for 3.8.
--b.
> if (lockowner_slab == NULL)
> goto out_nomem;
> file_slab = kmem_cache_create("nfsd4_files",
> --
> 1.7.4.4
>
prev parent reply other threads:[~2012-10-24 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 6:44 [PATCH] nfs: fix wrong object type in lockowner_slab ycnian
2012-10-24 19:42 ` J. Bruce Fields [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=20121024194224.GB6697@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=ycnian@gmail.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;
as well as URLs for NNTP newsgroup(s).