From: Wei Yang <richard.weiyang@gmail.com>
To: qiwuchen55@gmail.com
Cc: akpm@linux-foundation.org, willy@infradead.org, david@redhat.com,
richard.weiyang@gmail.com, mhocko@suse.com,
pankaj.gupta.linux@gmail.com, yang.shi@linux.alibaba.com,
cai@lca.pw, bhe@redhat.com, linux-mm@kvack.org,
chenqiwu <chenqiwu@xiaomi.com>
Subject: Re: [RESEND PATCH 1/3] mm: Replace zero-length array with flexible-array member
Date: Sat, 11 Apr 2020 13:54:29 +0000 [thread overview]
Message-ID: <20200411135429.u36ii6vv5nkscxrz@master> (raw)
In-Reply-To: <1586599916-15456-1-git-send-email-qiwuchen55@gmail.com>
On Sat, Apr 11, 2020 at 06:11:54PM +0800, qiwuchen55@gmail.com wrote:
>From: chenqiwu <chenqiwu@xiaomi.com>
>
>The current codebase makes use of the zero-length array language
>extension to the C90 standard, but the preferred mechanism to declare
>variable-length types such as these ones is a flexible array member[1][2],
>introduced in C99:
>
>struct foo {
> int stuff;
> struct boo array[];
>};
>
>By making use of the mechanism above, we will get a compiler warning
>in case the flexible array does not occur last in the structure, which
>will help us prevent some kind of undefined behavior bugs from being
>inadvertently introduced[3] to the codebase from now on.
>
>Also, notice that, dynamic memory allocations won't be affected by
>this change:
>
>"Flexible array members have incomplete type, and so the sizeof operator
>may not be applied. As a quirk of the original implementation of
>zero-length arrays, sizeof evaluates to zero."[1]
>
>This issue was found with the help of Coccinelle.
>
>[1] https://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html
>[2] https://github.com/KSPP/linux/issues/21
>[3] commit 76497732932f ("cxgb3/l2t: Fix undefined behaviour")
>
>Signed-off-by: chenqiwu <chenqiwu@xiaomi.com>
The change looks good to me.
Reviewed-by: Wei Yang <richard.weiyang@gmail.com>
>---
> include/linux/mm.h | 2 +-
> include/linux/mmzone.h | 2 +-
> include/linux/swap.h | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
>diff --git a/include/linux/mm.h b/include/linux/mm.h
>index 5a32342..9831bb5 100644
>--- a/include/linux/mm.h
>+++ b/include/linux/mm.h
>@@ -1718,7 +1718,7 @@ struct frame_vector {
> unsigned int nr_frames; /* Number of frames stored in ptrs array */
> bool got_ref; /* Did we pin pages by getting page ref? */
> bool is_pfns; /* Does array contain pages or pfns? */
>- void *ptrs[0]; /* Array of pinned pfns / pages. Use
>+ void *ptrs[]; /* Array of pinned pfns / pages. Use
> * pfns_vector_pages() or pfns_vector_pfns()
> * for access */
> };
>diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
>index 1b9de7d..f6b9fa9 100644
>--- a/include/linux/mmzone.h
>+++ b/include/linux/mmzone.h
>@@ -1147,7 +1147,7 @@ struct mem_section_usage {
> DECLARE_BITMAP(subsection_map, SUBSECTIONS_PER_SECTION);
> #endif
> /* See declaration of similar field in struct zone */
>- unsigned long pageblock_flags[0];
>+ unsigned long pageblock_flags[];
> };
>
> void subsection_map_init(unsigned long pfn, unsigned long nr_pages);
>diff --git a/include/linux/swap.h b/include/linux/swap.h
>index b835d8d..e1bbf7a 100644
>--- a/include/linux/swap.h
>+++ b/include/linux/swap.h
>@@ -275,7 +275,7 @@ struct swap_info_struct {
> */
> struct work_struct discard_work; /* discard worker */
> struct swap_cluster_list discard_clusters; /* discard clusters list */
>- struct plist_node avail_lists[0]; /*
>+ struct plist_node avail_lists[]; /*
> * entries in swap_avail_heads, one
> * entry per node.
> * Must be last as the number of the
>--
>1.9.1
--
Wei Yang
Help you, Help me
prev parent reply other threads:[~2020-04-11 13:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 10:11 qiwuchen55
2020-04-11 10:11 ` [RESEND PATCH 2/3] mm/swapfile: use list_{prev,next}_entry() instead of open-coding qiwuchen55
2020-04-11 10:11 ` [RESEND PATCH 3/3] mm/vmscan: make several optimizations for isolate_lru_pages() qiwuchen55
2020-04-11 16:10 ` Matthew Wilcox
2020-04-12 7:35 ` chenqiwu
2020-04-12 10:18 ` Matthew Wilcox
2020-04-11 13:54 ` Wei Yang [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=20200411135429.u36ii6vv5nkscxrz@master \
--to=richard.weiyang@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=cai@lca.pw \
--cc=chenqiwu@xiaomi.com \
--cc=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=pankaj.gupta.linux@gmail.com \
--cc=qiwuchen55@gmail.com \
--cc=willy@infradead.org \
--cc=yang.shi@linux.alibaba.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