> I don't think it is a good approach to do anything related to 5142
> different functions at once.
A source code search with the following pattern found only six functions for
further consideration.
@is_unnecessary_check@
expression data;
identifier work;
identifier release =~ "^kz?free$";
position pos;
type t;
@@
t work@pos(...)
{
...
( if (data) release(data);
| if (likely(data)) release(data);
)
...
}
I wonder a bit about this analysis result because the SmPL pattern I started
this discussion thread with showed a few more update candidates.
> It would be better to pick a small set of functions, and work on them
> carefully.
I would prefer to handle a more complete fix pattern.
By the way: I read about corresponding software update approaches in an article
"Best practices for a big patch series" by Wolfram Sang.
How are the chances to resolve the message "Fatal error: exception
Pcre.Error(_)" with a proposed long alternation?
Regards,
Markus
_______________________________________________
Cocci mailing list
[email protected]
https://systeme.lip6.fr/mailman/listinfo/cocci
