On 1/28/21 2:54 PM, Jonas Große Sundrup wrote: > On 2020-09-05, John Johansen wrote: >> This would point to a kernel change. Do you know how to bisect? Or are >> you willing to test debug kernels built for you based on a bisect. > > Yes, unfortunately due to time constraints I didn't get around to > bisecting the problem just yet. I, however, also noticed that the > problem is gone by now, so I suspect the underlying issue has been be > resolved, possibly intentionally or as a drive-by effect of another fix. > > Either way I would consider this fixed and let it be, unless you would > say that we should still investigate the details of this problem > further. For the record: I'm currently on Linux 5.10.10. > > Many thanks for the help nevertheless, as well as for building and > maintaining AppArmor! > thanks for reporting back. I am definitely interested in finding out what fixed this, to make sure it gets backported, but there is a good chance it has been tagged as a fix already and will make it into stable.
With that said I don't have a lot of time (none really) to chase this especially if its fixed so unless you find the time to bisect it and report back I am willing to just be happy that it is fixed thanks for reporting and helping make apparmor better -- AppArmor mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/apparmor
