From: "Gustavo A. R. Silva" <gustavoars@kernel.org>
To: Joe Perches <joe@perches.com>
Cc: Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"x86@kernel.org H. Peter Anvin" <hpa@zytor.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH] x86/uv/time: Replace one-element array and save heap space
Date: Mon, 18 May 2020 17:32:02 -0500 [thread overview]
Message-ID: <20200518223202.GD9868@embeddedor> (raw)
In-Reply-To: <b03d196cdbbbc6e9e8456910c6c6673ab67f76cb.camel@perches.com>
On Mon, May 18, 2020 at 12:09:16PM -0700, Joe Perches wrote:
> On Mon, 2020-05-18 at 14:01 -0500, Gustavo A. R. Silva wrote:
> > The current codebase makes use of one-element arrays in the following
> > form:
> >
> > struct something {
> > int length;
> > u8 data[1];
> > };
> []
> > This issue has been out there since 2009.
> > This issue was found with the help of Coccinelle and fixed _manually_.
> []
> > diff --git a/arch/x86/platform/uv/uv_time.c b/arch/x86/platform/uv/uv_time.c
> > index 7af31b245636..993a8ae6fdfb 100644
> > --- a/arch/x86/platform/uv/uv_time.c
> > +++ b/arch/x86/platform/uv/uv_time.c
> > @@ -52,7 +52,7 @@ struct uv_rtc_timer_head {
> > struct {
> > int lcpu; /* systemwide logical cpu number */
> > u64 expires; /* next timer expiration for this cpu */
> > - } cpu[1];
> > + } cpu[];
> > };
> >
> > /*
> > @@ -156,9 +156,8 @@ static __init int uv_rtc_allocate_timers(void)
> > struct uv_rtc_timer_head *head = blade_info[bid];
> >
> > if (!head) {
> > - head = kmalloc_node(sizeof(struct uv_rtc_timer_head) +
> > - (uv_blade_nr_possible_cpus(bid) *
> > - 2 * sizeof(u64)),
> > + head = kmalloc_node(struct_size(head, cpu,
> > + uv_blade_nr_possible_cpus(bid)),
>
> It's probably safer to use kzalloc_node here as well.
>
Thanks for your feedback, Joe. I'll wait for comments from the
maintainers on this and the rest of the patch.
Thanks
--
Gustavo
> > GFP_KERNEL, nid);
> > if (!head) {
> > uv_rtc_deallocate_timers();
>
next prev parent reply other threads:[~2020-05-18 22:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 19:01 [PATCH] x86/uv/time: Replace one-element array and save heap space Gustavo A. R. Silva
2020-05-18 19:09 ` Joe Perches
2020-05-18 22:32 ` Gustavo A. R. Silva [this message]
2020-05-20 17:19 ` Kees Cook
2020-05-20 19:01 ` Joe Perches
2020-05-21 23:24 ` Gustavo A. R. Silva
2020-09-29 23:14 ` Gustavo A. R. Silva
2020-09-30 6:52 ` Thomas Gleixner
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=20200518223202.GD9868@embeddedor \
--to=gustavoars@kernel.org \
--cc=andy@infradead.org \
--cc=bp@alien8.de \
--cc=dvhart@infradead.org \
--cc=gustavo@embeddedor.com \
--cc=hpa@zytor.com \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.