slist: put the sm_state itself into ->possible not a copy of the sm_state
commit162aa09d3d08d67d1a5778af2e6f65137dc0c6df
authorDan Carpenter <dan.carpenter@oracle.com>
Sun, 27 May 2012 18:28:07 +0000 (27 21:28 +0300)
committerDan Carpenter <dan.carpenter@oracle.com>
Sun, 27 May 2012 18:28:07 +0000 (27 21:28 +0300)
tree0c8cbf2b59322d075bf014c8fd61f7ae99f71e46
parent0c9dd6f1a66730a88251b3544a1eed4ada426389
slist: put the sm_state itself into ->possible not a copy of the sm_state

This was a huge memory waster.  We did a bunch of needless copies with
merge_sm_state().  The add_sm_state() function doesn't even add the new
sm_state if it was already included.  With this change I don't have any
more places on my kernel build where I bailing because functions are too
complicated.

But another reason to do this is that I want the ->possible states to have
a valid ->pool pointer for some later work.

Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
smatch_slist.c