On Mon, 2008-04-07 at 14:55 -0700, Christopher Li wrote:
> On Mon, Apr 7, 2008 at 1:45 PM, Pavel Roskin <proski@xxxxxxx> wrote:
> > static int x;
> > static inline void foo(void)
> > {
> > if (x)
> > x = 1;
> > }
> > static void bar(void)
> > {
> > foo();
> > }
> > static typeof(bar) quux;
> >
> >
> > The crash happens in linearize_compound_statement(), and I believe that
> > the reason is incorrect access to phi_node->phi_list without making sure
> > that phi_node->opcode is OP_PHI. When processing the above program,
> > phi_node->phi_list can be OP_INLINED_CALL.
>
> No, that is not the root cause. The root cause is you feed sparse with
> bad input. typeof(bar) will give you a type of a function. Sparse just let
> quux have the base type of bar function body. That is just so wrong.
I know. And the source that was doing it is fixed long ago.
> > I understand very little in sparse code, and I have no idea what kind of
> > fallback is needed when phi_node->opcode is not OP_PHI.
> >
> > But this patch fixes the crash:
>
> As I said before, this is not the right fix. Wish it not get applied.
I should have been more clear. Last time I was carried away by some
strange messages about "return" and labels, which seemed really weird to
me, but less so after your explanation.
This example is made from the same original source, but this time I
concentrated on the crash, because that's the thing that cannot be
justified by any bad code.
> I agree sparse should not assert on it, but not like this.
I don't quite understand why sparse is getting in this situation, but
I'm quite confident from seeing other code that phi_node->phi_list is
invalid if phi_node->opcode is not OP_PHI, and should not be accessed.
I'd rather see sparse tripping an assert and crashing before it happens
rather than see it interpreting some other data as phi_list and crashing
randomly while iterating over that bogus list.
> You should at least fix it from the typeof(bar) side, instead of try
> to linearize
> the same function twice.
That's fixed, of course. And many other problems are fixed too, some of
which are user visible. I really appreciate the usefulness of sparse.
All I'm trying to do now is to have that crash fixed, after which I
would be glad to forget the ugly code that caused it.
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
