From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: Rick Edgecombe <rick.p.edgecombe@intel.com>,
Pavel Boldin <pboldin@cloudlinux.com>,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/2] stack_clash: Guard functions used only in 64bit
Date: Wed, 25 Oct 2023 11:29:42 +0200 [thread overview]
Message-ID: <ZTjgBkVwwvqgbWm1@rei> (raw)
In-Reply-To: <20231024084923.217110-1-pvorel@suse.cz>
Hi!
> To avoid "defined but not used" warnings when compiled on 32bit.
>
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> testcases/cve/stack_clash.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/testcases/cve/stack_clash.c b/testcases/cve/stack_clash.c
> index 3a99c49bb..56b970a1b 100644
> --- a/testcases/cve/stack_clash.c
> +++ b/testcases/cve/stack_clash.c
> @@ -92,6 +92,7 @@ void segv_handler(int sig, siginfo_t *info, void *data LTP_ATTRIBUTE_UNUSED)
> _exit(EXIT_SUCCESS);
> }
>
> +#ifdef __x86_64__
> static void force_bottom_up(void)
> {
> FILE *fh;
> @@ -134,6 +135,7 @@ static void force_bottom_up(void)
> out:
> SAFE_FCLOSE(fh);
> }
> +#endif
Maybe I'm blind but this function does not seem to be called from inside
of #ifdef __x86_64__.
> unsigned long read_stack_addr_from_proc(unsigned long *stack_size)
> {
> @@ -187,6 +189,7 @@ void __attribute__((noinline)) preallocate_stack(unsigned long required)
> garbage[0] = garbage[required - 1] = '\0';
> }
>
> +#ifdef __x86_64__
> static void do_mmap_placement_test(unsigned long stack_addr, unsigned long gap)
> {
> void *map_test_gap;
> @@ -208,6 +211,7 @@ static void do_mmap_placement_test(unsigned long stack_addr, unsigned long gap)
> SAFE_MUNMAP(map_test_gap, MAPPED_LEN);
> }
> }
> +#endif
This part looks good.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-10-25 9:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 8:49 [LTP] [PATCH 1/2] stack_clash: Guard functions used only in 64bit Petr Vorel
2023-10-24 8:49 ` [LTP] [PATCH 2/2] stack_clash: Compile with -Wno-infinite-recursion Petr Vorel
2023-10-25 9:30 ` Cyril Hrubis
2023-10-25 23:15 ` Petr Vorel
2023-10-25 9:29 ` Cyril Hrubis [this message]
2023-10-25 23:14 ` [LTP] [PATCH 1/2] stack_clash: Guard functions used only in 64bit Petr Vorel
2023-10-26 8:43 ` Cyril Hrubis
2023-10-26 9:37 ` Petr Vorel
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=ZTjgBkVwwvqgbWm1@rei \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pboldin@cloudlinux.com \
--cc=pvorel@suse.cz \
--cc=rick.p.edgecombe@intel.com \
/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