db/fixup_kernel.sh: work around for gfs2_ea_find()
commit3f40b5d767745c35bc798c7406bdcdca15d15b23
authorDan Carpenter <dan.carpenter@oracle.com>
Fri, 15 Jul 2016 13:46:45 +0000 (15 16:46 +0300)
committerDan Carpenter <dan.carpenter@oracle.com>
Sat, 16 Jul 2016 21:44:53 +0000 (17 00:44 +0300)
tree52d47c160a75f55ebe304bb980a9b5e59de7a0cb
parent6d73618cc6a764365ea76cb934c90302836619d7
db/fixup_kernel.sh: work around for gfs2_ea_find()

It would be better if this wasn't needed, of course.  What happens is this:

We pass in "el".

        ef.ef_el = el;
        memset(el, 0, sizeof(struct gfs2_ea_location));
        error = ea_foreach(ip, ea_find_i, &ef);

Smatch sees that we memset "el".  But ea_foreach() treats "ef" as a void
pointer to data.  Smatch marks it as an untracked parameter.  But smatch
doesn't make the jump from ef.ef_el back to el.  So the caller says that
everything in el is set to zero.

Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
smatch_data/db/fixup_kernel.sh