From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Increasing usage of array allocation functions with SmPL
Date: Sat, 30 Jun 2018 13:30:24 +0200 [thread overview]
Message-ID: <4e2c98c2-0411-ff79-143b-3be2b9930913@users.sourceforge.net> (raw)
In-Reply-To: <CAGXu5j+XA87CBA9Xbqb4C-wLndaNW+usPgA9043m4TDeFUcxpw@mail.gmail.com>
> I've been doing some large treewide changes to the allocators,
I find your update suggestion ?mm: Use overflow helpers in kmalloc_array*()? interesting.
https://lkml.org/lkml/2018/5/31/877
https://patchwork.kernel.org/patch/10442283/
https://lkml.kernel.org/r/<20180601004233.37822-7-keescook@chromium.org>
It seems that corresponding work became noteworthy news ?4.18 Merge window, part 2?.
https://lwn.net/Articles/757187/
Now I am curious on how software evolution will be continued according to such
a transformation pattern.
https://patchwork.kernel.org/project/LKML/list/?state=*&q=alloc_array
> and I notice that Coccinelle does something odd for a specific case.
Will there happen any more evolution in this software area?
Regards,
Markus
prev parent reply other threads:[~2018-06-30 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 23:17 [Cocci] Weird whitespace behavior? Kees Cook
2018-06-12 2:38 ` Kees Cook
2018-06-12 4:54 ` Julia Lawall
2018-06-30 11:30 ` 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=4e2c98c2-0411-ff79-143b-3be2b9930913@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=cocci@systeme.lip6.fr \
/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).