From: Kees Cook <keescook@chromium.org>
To: cocci@inria.fr
Subject: [cocci] how to check a for "don't care" state of a variable?
Date: Fri, 7 Oct 2022 16:11:44 -0700 [thread overview]
Message-ID: <202210071600.078A2101@keescook> (raw)
Hi!
I was looking at doing some conversions for this[1], and I wasn't sure
how to check for removing a variable assignment if there was either no
more uses or the next use was an assignment itself.
i.e.:
var = 1;
other = func(var);
turns into:
other = func(1);
but this would not:
var = 1;
other = func(var);
report(var);
without getting confused by:
var = 1;
other = func(var);
var = 5;
@multi_line@
identifier randfunc =~ "get_random_int|prandom_u32|get_random_u32";
identifier RAND;
expression E;
type TYPE;
@@
(
- RAND = randfunc();
... when != RAND
- RAND %= (E);
+ RAND = prandom_u32_max(E);
|
- RAND = randfunc();
... when != RAND
- ((TYPE)RAND % (E))
+ prandom_u32_max(E)
// This is wrong: we need to check that RAND is either assigned or never
// accessed again
)
I thought I could do this:
... when != RAND
<... RAND = EXP; ...>
But this appears to be invalid syntax...
-Kees
[1] https://lore.kernel.org/lkml/202210071241.445289C5@keescook/
--
Kees Cook
WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org>
To: cocci@inria.fr
Cc: Julia Lawall <julia.lawall@inria.fr>,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: [cocci] how to check a for "don't care" state of a variable?
Date: Fri, 7 Oct 2022 20:09:40 -0700 [thread overview]
Message-ID: <202210071600.078A2101@keescook> (raw)
Message-ID: <20221008030940.2HhllfgyLDfrTnU9FXA3o0RVKTTJwIYaIDYHj5k85ZM@z> (raw)
Hi!
I was looking at doing some conversions for this[1], and I wasn't sure
how to check for removing a variable assignment if there was either no
more uses or the next use was an assignment itself.
i.e.:
var = 1;
other = func(var);
turns into:
other = func(1);
but this would not:
var = 1;
other = func(var);
report(var);
without getting confused by:
var = 1;
other = func(var);
var = 5;
@multi_line@
identifier randfunc =~ "get_random_int|prandom_u32|get_random_u32";
identifier RAND;
expression E;
type TYPE;
@@
(
- RAND = randfunc();
... when != RAND
- RAND %= (E);
+ RAND = prandom_u32_max(E);
|
- RAND = randfunc();
... when != RAND
- ((TYPE)RAND % (E))
+ prandom_u32_max(E)
// This is wrong: we need to check that RAND is either assigned or never
// accessed again
)
I thought I could do this:
... when != RAND
<... RAND = EXP; ...>
But this appears to be invalid syntax...
-Kees
[1] https://lore.kernel.org/lkml/202210071241.445289C5@keescook/
--
Kees Cook
next reply other threads:[~2022-10-08 7:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 23:11 Kees Cook [this message]
2022-10-08 3:09 ` [cocci] how to check a for "don't care" state of a variable? Kees Cook
2022-10-08 7:43 ` Julia Lawall
2022-10-08 8:55 ` Markus Elfring
2022-10-08 9:00 ` Julia Lawall
2022-10-08 9:15 ` Markus Elfring
2022-10-08 11:02 ` Markus Elfring
2022-10-09 15:10 ` Kees Cook
2022-10-09 15:12 ` Julia Lawall
2022-10-09 15:56 ` Markus Elfring
2022-10-09 17:37 ` Kees Cook
2022-10-09 18:02 ` Julia Lawall
2022-10-09 18:16 ` Kees Cook
2022-10-09 18:19 ` Julia Lawall
2022-10-10 2:16 ` Jason A. Donenfeld
2022-10-10 19:12 ` [cocci] Reconsidering selected SmPL code Markus Elfring
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=202210071600.078A2101@keescook \
--to=keescook@chromium.org \
--cc=cocci@inria.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 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.