From: Pavel Roskin <proski@gnu.org>
To: Kamil Dudka <kdudka@redhat.com>
Cc: Christopher Li <sparse@chrisli.org>, linux-sparse@vger.kernel.org
Subject: Re: Sparse crash when mixing int and enum in ternary operator
Date: Tue, 09 Mar 2010 13:35:19 -0500 [thread overview]
Message-ID: <1268159719.23196.12.camel@mj> (raw)
In-Reply-To: <201003091446.50092.kdudka@redhat.com>
On Tue, 2010-03-09 at 14:46 +0100, Kamil Dudka wrote:
P.S. Sorry, I just realized I could add more useful information. That's
the complete expr in warn_for_enum_conversions():
(gdb) p *expr
$4 = {type = EXPR_CONDITIONAL, flags = 0, op = 63, pos = {type = 7,
stream = 3, newline = 0, whitespace = 1, pos = 47, line = 897, noexpand
= 0}, ctype = 0x668bc0, {{value = 139893141633168, taint = 0,
enum_type = 0x7f3b6a387b10}, fvalue = 0, string = 0x7f3b69037890,
{unop = 0x7f3b69037890, op_value = 0}, {symbol = 0x7f3b69037890,
symbol_name = 0x0}, statement = 0x7f3b69037890, {left = 0x7f3b69037890,
right = 0x0}, {deref = 0x7f3b69037890, member = 0x0}, {base =
0x7f3b69037890, r_bitpos = 0, r_nrbits = 0}, {cast_type =
0x7f3b69037890, cast_expression = 0x0}, {conditional = 0x7f3b69037890,
cond_true = 0x0, cond_false = 0x7f3b6a387b10}, {fn =
0x7f3b69037890, args = 0x0}, {label_symbol = 0x7f3b69037890}, expr_list
= 0x7f3b69037890, {expr_ident = 0x7f3b69037890, field = 0x0,
ident_expression = 0x7f3b6a387b10}, {idx_from = 1761835152, idx_to
= 32571, idx_expression = 0x0}, {init_offset = 1761835152, init_nr =
32571, init_expr = 0x0}, {in = 0x7f3b69037890, down = 0x0, {
ident = 0x7f3b6a387b10, index = 0x7f3b6a387b10}}}}
And that's where it happens (in the code being checked):
static int do_alg_test(const char *alg, u32 type, u32 mask)
{
return crypto_has_alg(alg, type, mask ?: CRYPTO_ALG_TYPE_MASK) ?
0 : -ENOENT;
}
I removed the outside conditional, and sparse would still crash on this:
crypto_has_alg(alg, type, mask ?: CRYPTO_ALG_TYPE_MASK);
but not on this:
crypto_has_alg(alg, type, mask ? mask: CRYPTO_ALG_TYPE_MASK);
Apparently, the "?:" notation is confusing sparse now.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2010-03-09 18:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 1:24 Sparse crash when mixing int and enum in ternary operator Pavel Roskin
2010-03-09 5:43 ` Christopher Li
2010-03-09 13:46 ` Kamil Dudka
2010-03-09 18:26 ` Pavel Roskin
2010-03-09 18:35 ` Pavel Roskin [this message]
2010-03-09 19:06 ` Kamil Dudka
2010-03-09 19:15 ` Josh Triplett
2010-03-09 20:11 ` Pavel Roskin
2010-03-09 20:29 ` Kamil Dudka
2010-03-09 23:30 ` Kamil Dudka
2010-03-10 1:09 ` Pavel Roskin
2010-03-10 16:05 ` Kamil Dudka
2010-03-10 20:27 ` Pavel Roskin
2010-03-10 20:44 ` Kamil Dudka
2010-03-10 21:03 ` Kamil Dudka
2010-03-10 21:56 ` Christopher Li
2010-03-13 17:22 ` Kamil Dudka
2010-03-21 15:27 ` Kamil Dudka
2010-03-24 10:07 ` Christopher Li
2010-03-24 10:51 ` Kamil Dudka
2010-03-27 9:16 ` Kamil Dudka
2010-03-27 9:29 ` Josh Triplett
2010-03-27 9:53 ` [PATCH] eliminate insane conversions from int to enum Kamil Dudka
2010-03-29 18:11 ` Christopher Li
2010-03-29 18:05 ` Sparse crash when mixing int and enum in ternary operator Christopher Li
2010-03-29 18:17 ` Kamil Dudka
2010-03-29 18:48 ` Christopher Li
2010-03-29 19:23 ` Kamil Dudka
2010-03-30 5:29 ` Pavel Roskin
2010-03-29 21:26 ` Josh Triplett
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=1268159719.23196.12.camel@mj \
--to=proski@gnu.org \
--cc=kdudka@redhat.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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).