From: Cyril Hrubis <chrubis@suse.cz>
To: Shirisha G <shirisha@linux.ibm.com>
Cc: geetika@linux.ibm.com, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] Migrating the libhugetlbfs/testcases/truncate.c test
Date: Fri, 8 Sep 2023 14:15:41 +0200 [thread overview]
Message-ID: <ZPsQbSsR1Y-zJBVd@yuki> (raw)
In-Reply-To: <20230908103921.511595-1-shirisha@linux.ibm.com>
Hi!
> +/*\
> + * [Description]
> + *
> + * Test Name: truncate
> + * Test case is used to verify the correct functionality
> + * and compatibility of the library with the "truncate" system call when
> + * operating on files residing in a mounted huge page filesystem.
> + */
> +
> +#include "hugetlb.h"
> +
> +#define RANDOM_CONSTANT 0x1234ABCD
^
THis is not used at all.
> +#define MNTPOINT "hugetlbfs/"
> +long hpage_size;
> +int fd;
These two should be static.
> +
> +
> +static void sigbus_handler(int signum LTP_ATTRIBUTE_UNUSED)
> +{
> + tst_res(TPASS, "Test Passed");
> + exit(0);
It's not safe to call exit(0) from a signal handler.
What should be done instead is to:
- add global static volatile int variable
- reset it before we attempt to access the truncated memory
- set it in the signal handler
- print TPASS/TFAIL based on the value of the variable in the run_test()
function
> +}
> +
> +static void run_test(void)
> +{
> + void *p;
> + volatile unsigned int *q;
^
I do not think that this has to be volatile.
All in all this can be just:
unsigned int *p;
...
p = SAFE_MMAP();
...
*p = 0;
> + struct sigaction my_sigaction;
> + my_sigaction.sa_handler = sigbus_handler;
> + p = SAFE_MMAP(NULL, hpage_size, PROT_READ|PROT_WRITE, MAP_SHARED,
> + fd, 0);
> + if (p == MAP_FAILED)
> + tst_res(TFAIL, "mmap failed..!!");
SAFE_MMAP() cannot fail, it does exit the test with a failure if the it
fails to map the memory.
> + q = p;
> + *q = 0;
> + SAFE_SIGACTION(SIGBUS, &my_sigaction, NULL);
I guess that we can set up the handler in the setup instead.
> + SAFE_FTRUNCATE(fd, 0);
> + *q;
> + tst_res(TFAIL, "Didn't SIGBUS");
And we should SAFE_UNMAP() the memory here.
Also does the test work with -i 2 ?
> +}
> +
> +
> +void setup(void)
> +{
> + hpage_size = tst_get_hugepage_size();
> + fd = tst_creat_unlinked(MNTPOINT, 0);
^
Wrong indentation, please make sure to run 'make check' and fix all
the reported problems.
> +}
> +
> +void cleanup(void)
> +{
> + if (fd > 0)
> + SAFE_CLOSE(fd);
> +}
> +
> +static struct tst_test test = {
> + .needs_root = 1,
> + .mntpoint = MNTPOINT,
> + .needs_hugetlbfs = 1,
> + .needs_tmpdir = 1,
> + .setup = setup,
> + .cleanup = cleanup,
> + .test_all = run_test,
> + .hugepages = {1, TST_NEEDS},
> +};
> --
> 2.39.3
>
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-09-08 12:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 10:39 [LTP] [PATCH v2] Migrating the libhugetlbfs/testcases/truncate.c test Shirisha G
2023-09-08 12:15 ` Cyril Hrubis [this message]
2023-09-29 8:50 ` Shirisha ganta
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=ZPsQbSsR1Y-zJBVd@yuki \
--to=chrubis@suse.cz \
--cc=geetika@linux.ibm.com \
--cc=ltp@lists.linux.it \
--cc=shirisha@linux.ibm.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