[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1807011100110.2748@hadrien>
Date: Sun, 1 Jul 2018 11:03:29 +0200 (CEST)
From: Julia Lawall <julia.lawall@...6.fr>
To: SF Markus Elfring <elfring@...rs.sourceforge.net>
cc: Kees Cook <keescook@...omium.org>, Matthew Wilcox <mawilcox@...rosoft.com>,
linux-mm@...ck.org, kernel-hardening@...ts.openwall.com,
kernel-janitors@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
Matthew Wilcox <willy@...radead.org>,
Rasmus Villemoes <linux@...musvillemoes.dk>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH v3 12/16] treewide: Use array_size() for
kmalloc()-family
> > // 2-factor product with sizeof(variable)
> > @@
> > identifier alloc =~ "kmalloc|kzalloc|kvmalloc|kvzalloc";
>
> * This regular expression could be optimised to the specification “kv?[mz]alloc”.
> Extensions will be useful for further function names.
>
> * The repetition of such a constraint in subsequent SmPL rules could be avoided
> if inheritance will be used for this metavariable.
This is quite incorrect. Inheritance is only possible when a match of the
previous rule has succeeded. If a rule never applies in a given file, the
rules that inherit from it won't apply either. Furthermore, what is
inherited is the value, not the constraint. If the original binding of
alloc only ever matches kmalloc, then the inherited references will only
match kmalloc too.
julia
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
