From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Kees Cook <keescook@chromium.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Ingo Molnar <mingo@redhat.com>, "x86@kernel.org" <x86@kernel.org>,
Dave Young <dyoung@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Matt Fleming <matt.fleming@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Julia Lawall <julia.lawall@lip6.fr>
Subject: Re: x86-ksysfs: Use kmalloc_array() in create_setup_data_nodes()
Date: Wed, 7 Sep 2016 18:55:09 +0200 [thread overview]
Message-ID: <6f626c15-aac1-a0ad-402a-425874e4908e@users.sourceforge.net> (raw)
In-Reply-To: <CAGXu5jJ=YsdYegd3L2RzPKA9OGxE2vzo7U8BQjgK+qAaxEu0pQ@mail.gmail.com>
> Fixing these kmalloc calls would be a nice thing to clean up everywhere.
Thanks for your acknowledgement of such a software improvement opportunity.
> Since it is a mistake people may continue to make, I think it would
> make sense to add a coccinelle script that can do this to the
> existing coccinelle scripts in the kernel if one to do it does not
> already exist. That way, it will be part of the coccinelle checking
> that is automatically run on the kernel regularly.
I am curious on how many contributors would like to help a bit more
in such a software development task.
How do you think about to clarify corresponding challenges better?
Do you find any details interesting which are described in a feature
request (or article) like "Improve determination of sizes with SmPL"?
https://github.com/coccinelle/coccinelle/issues/80
Regards,
Markus
prev parent reply other threads:[~2016-09-07 16:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 20:23 [PATCH] x86-ksysfs: Use kmalloc_array() in create_setup_data_nodes() SF Markus Elfring
2016-09-06 21:49 ` Kees Cook
2016-09-07 7:49 ` SF Markus Elfring
2016-09-07 10:36 ` Paolo Bonzini
2016-09-07 11:17 ` SF Markus Elfring
2016-09-07 11:20 ` Paolo Bonzini
2016-09-07 11:45 ` SF Markus Elfring
2016-09-07 16:23 ` Kees Cook
2016-09-07 16:37 ` Joe Perches
2016-09-07 17:01 ` Kees Cook
2016-09-07 16:55 ` SF Markus Elfring [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=6f626c15-aac1-a0ad-402a-425874e4908e@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=julia.lawall@lip6.fr \
--cc=keescook@chromium.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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).