On Mon, Aug 31, 2015 at 06:06:11PM -0700, Steve Beattie wrote: > Possible. It turns out this portion of the parser code wasn't exercised > enough, as many tests failed, but only on i386 where it segfaults > when a new cache object is not needed/created but then an attempt is > made to unref it -- we apparently got "lucky" on x86-64. The following > patch should address it: > > Signed-off-by: Steve Beattie <[email protected]> > --- > parser/parser_main.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > Index: b/parser/parser_main.c > =================================================================== > --- a/parser/parser_main.c > +++ b/parser/parser_main.c > @@ -860,7 +860,7 @@ static void setup_flags(void) > int main(int argc, char *argv[]) > { > aa_kernel_interface *kernel_interface = NULL; > - aa_policy_cache *policy_cache; > + aa_policy_cache *policy_cache = NULL; > int retval, last_error; > int i; > int optind; >
Nice find. Acked-by: Seth Arnold <[email protected]> Thanks
signature.asc
Description: Digital signature
-- AppArmor mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/apparmor
