From: Petr Vorel <pvorel@suse.cz>
To: David Hildenbrand <david@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] security/dirtyc0w_shmem: Fix remaining cases where UFFD_FEATURE_MINOR_SHMEM is absent
Date: Fri, 25 Nov 2022 12:12:35 +0100 [thread overview]
Message-ID: <Y4CjI7S/MHnQa7ex@pevik> (raw)
In-Reply-To: <20221125105201.59048-1-david@redhat.com>
Hi David,
> When UFFD_FEATURE_MINOR_SHMEM is not defined, we still have to make the
> checkpoint happy, otherwise our parent process will run into a timeout.
> Further, we have to test if UFFD_FEATURE_MINOR_SHMEM is really returned by
> the UFFD_API ioctl: if the kernel knows about the feature but doesn't
> support it, it will be masked off.
> Reported-by: Martin Doucha <mdoucha@suse.cz>
> Cc: Petr Vorel <pvorel@suse.cz>
> Cc: Cyril Hrubis <chrubis@suse.cz>
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
> .../dirtyc0w_shmem/dirtyc0w_shmem_child.c | 16 ++++++++++++----
> 1 file changed, 12 insertions(+), 4 deletions(-)
> diff --git a/testcases/kernel/security/dirtyc0w_shmem/dirtyc0w_shmem_child.c b/testcases/kernel/security/dirtyc0w_shmem/dirtyc0w_shmem_child.c
> index cb2e9df0c..c117c6f39 100644
> --- a/testcases/kernel/security/dirtyc0w_shmem/dirtyc0w_shmem_child.c
> +++ b/testcases/kernel/security/dirtyc0w_shmem/dirtyc0w_shmem_child.c
> @@ -24,12 +24,12 @@
> #include <linux/userfaultfd.h>
> #endif
> -#ifdef UFFD_FEATURE_MINOR_SHMEM
Shouldn't be the check and TST_TEST_TCONF() actually be in dirtyc0w_shmem.c?
I overlooked that, but IMHO test does not make sense at all if
UFFD_FEATURE_MINOR_SHMEM not defined, right?
Also Martin noted that ("The parent process should not even fork() when
UFFD_FEATURE_MINOR_SHMEM is not defined in config.h.").
Therefore one fix would be to move the check to parent and second
(maybe better in separate commit) to add check for uffdio_api.features.
Kind regards,
Petr
> -
> #define TST_NO_DEFAULT_MAIN
> #include "tst_test.h"
> #include "tst_safe_macros.h"
> #include "tst_safe_pthread.h"
> +
> +#ifdef UFFD_FEATURE_MINOR_SHMEM
> #include "lapi/syscalls.h"
> #define TMP_DIR "tmp_dirtyc0w_shmem"
> @@ -162,6 +162,10 @@ retry:
> "Could not create userfault file descriptor");
> }
> + if (!(uffdio_api.features & UFFD_FEATURE_MINOR_SHMEM))
> + tst_brk(TCONF,
> + "System does not have userfaultfd minor fault support for shmem");
> +
> uffdio_register.range.start = (unsigned long) map;
> uffdio_register.range.len = page_size;
> uffdio_register.mode = UFFDIO_REGISTER_MODE_MINOR;
> @@ -236,6 +240,10 @@ int main(void)
> return 0;
> }
> #else /* UFFD_FEATURE_MINOR_SHMEM */
> -#include "tst_test.h"
> -TST_TEST_TCONF("System does not have userfaultfd minor fault support for shmem");
> +int main(void)
> +{
> + tst_reinit();
> + TST_CHECKPOINT_WAKE(0);
> + tst_brk(TCONF, "System does not have userfaultfd minor fault support for shmem");
> +}
> #endif /* UFFD_FEATURE_MINOR_SHMEM */
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-11-25 11:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 10:52 [LTP] [PATCH v1] security/dirtyc0w_shmem: Fix remaining cases where UFFD_FEATURE_MINOR_SHMEM is absent David Hildenbrand
2022-11-25 11:12 ` Petr Vorel [this message]
2022-11-25 11:16 ` David Hildenbrand
2022-11-25 12:34 ` Petr Vorel
2022-11-25 11:20 ` Martin Doucha
2022-11-25 12:19 ` David Hildenbrand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y4CjI7S/MHnQa7ex@pevik \
--to=pvorel@suse.cz \
--cc=david@redhat.com \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox