On Fri, Oct 18, 2024 at 12:32:37PM -0700, Jeff Xu wrote: > > when they encouter a failure, the pattern I sketched in my earlier > > message, or switch to kselftest_harness.h (like I say I don't know if > > the fork()ing is an issue for these tests). If I had to have a macro > > it'd probably be something like mseal_assert(). > > > I can go with mseal_assert, the original macro is used by mseal_test > itself, and only intended as such. > > If changing name to mseal_assert() is acceptable, this seems to be a > minimum change and I'm happy with that. No.