[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <736fefd9-4bce-4aec-a492-2267fdc83776@lucifer.local>
Date: Fri, 18 Oct 2024 20:52:38 +0100
From: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
To: Jeff Xu <jeffxu@...omium.org>
Cc: Mark Brown <broonie@...nel.org>,
Muhammad Usama Anjum <usama.anjum@...labora.com>,
akpm@...ux-foundation.org, linux-kselftest@...r.kernel.org,
linux-mm@...ck.org, linux-hardening@...r.kernel.org,
linux-kernel@...r.kernel.org, pedro.falcato@...il.com,
willy@...radead.org, vbabka@...e.cz, Liam.Howlett@...cle.com,
rientjes@...gle.com, keescook@...omium.org
Subject: Re: [PATCH v3 4/5] selftests/mseal: add more tests for mmap
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.
Powered by blists - more mailing lists