From: Joseph Qi <jiangqi903@gmail.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Mark Fasheh <mark@fasheh.com>, Joel Becker <jlbec@evilplan.org>,
akpm <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
ocfs2-devel@lists.linux.dev,
Joseph Qi <joseph.qi@linux.alibaba.com>
Subject: Re: [PATCH 1/2] ocfs2: Use flexible array in 'struct ocfs2_recovery_map'
Date: Mon, 17 Jul 2023 10:15:28 +0800 [thread overview]
Message-ID: <1522806a-ee51-04d5-0c78-6cf0e1c0eaf3@gmail.com> (raw)
In-Reply-To: <c645911ffd2720fce5e344c17de642518cd0db52.1689533270.git.christophe.jaillet@wanadoo.fr>
On 7/17/23 2:48 AM, Christophe JAILLET wrote:
> Turn 'rm_entries' in 'struct ocfs2_recovery_map' into a flexible array.
>
> The advantages are:
> - save the size of a pointer when the new undo structure is allocated
> - avoid some always ugly pointer arithmetic to get the address of
> 'rm_entries'
> - avoid an indirection when the array is accessed
>
> While at it, use struct_size() to compute the size of the new undo
> structure.
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Looks fine.
Reviewed-by: Joseph Qi <joseph.qi@linux.alibaba.com>
> ---
> fs/ocfs2/journal.c | 5 +----
> fs/ocfs2/journal.h | 2 +-
> 2 files changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/fs/ocfs2/journal.c b/fs/ocfs2/journal.c
> index 25d8072ccfce..2f7e70109020 100644
> --- a/fs/ocfs2/journal.c
> +++ b/fs/ocfs2/journal.c
> @@ -178,16 +178,13 @@ int ocfs2_recovery_init(struct ocfs2_super *osb)
> osb->recovery_thread_task = NULL;
> init_waitqueue_head(&osb->recovery_event);
>
> - rm = kzalloc(sizeof(struct ocfs2_recovery_map) +
> - osb->max_slots * sizeof(unsigned int),
> + rm = kzalloc(struct_size(rm, rm_entries, osb->max_slots),
> GFP_KERNEL);
> if (!rm) {
> mlog_errno(-ENOMEM);
> return -ENOMEM;
> }
>
> - rm->rm_entries = (unsigned int *)((char *)rm +
> - sizeof(struct ocfs2_recovery_map));
> osb->recovery_map = rm;
>
> return 0;
> diff --git a/fs/ocfs2/journal.h b/fs/ocfs2/journal.h
> index 41c382f68529..41c9fe7e62f9 100644
> --- a/fs/ocfs2/journal.h
> +++ b/fs/ocfs2/journal.h
> @@ -29,7 +29,7 @@ struct ocfs2_dinode;
>
> struct ocfs2_recovery_map {
> unsigned int rm_used;
> - unsigned int *rm_entries;
> + unsigned int rm_entries[];
> };
>
>
prev parent reply other threads:[~2023-07-17 2:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 18:48 Christophe JAILLET
2023-07-16 18:48 ` [PATCH 2/2] ocfs2: Use struct_size() Christophe JAILLET
2023-07-17 2:16 ` Joseph Qi
2023-07-17 2:15 ` Joseph Qi [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=1522806a-ee51-04d5-0c78-6cf0e1c0eaf3@gmail.com \
--to=jiangqi903@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
/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
all inboxes | Powered by JetHome®