From: Richard Palethorpe <rpalethorpe@suse.de>
To: Tarun Sahu <tsahu@linux.ibm.com>
Cc: aneesh.kumar@linux.ibm.com, vaibhav@linux.ibm.com,
sbhat@linux.ibm.com, ltp@lists.linux.it, geetika@linux.ibm.com
Subject: Re: [LTP] [PATCH 1/8] Hugetlb: Migrating libhugetlbfs fork-cow
Date: Thu, 08 Dec 2022 08:54:19 +0000 [thread overview]
Message-ID: <87sfhqqnpo.fsf@suse.de> (raw)
In-Reply-To: <20221207124758.e75o72ozwltbchyb@tarunpc>
Hello,
Tarun Sahu <tsahu@linux.ibm.com> writes:
> Hi,
> Thanks for reviewing it.
> On Dec 05 2022, Richard Palethorpe wrote:
>> Hello,
>>
>> Tarun Sahu <tsahu@linux.ibm.com> writes:
>>
>> > +
>> > +#include <sys/wait.h>
>> > +#include <sys/mman.h>
>> > +#include <stdlib.h>
>> > +#include <unistd.h>
>> > +#include <sys/types.h>
>> > +
>> > +#include "hugetlb.h"
>> > +
>> > +#define RANDOM_CONSTANT 0x1234ABCD
>> > +#define OTHER_CONSTANT 0xfeef5678
>>
>> It seems their are actually 3 constants as "random" is inverted. I'd
>> prefer it if they had names like C1, C2, C3 with no connotations.
>>
> Yeah, Will be more cleaner, Will update it.
>
> --skip
>> > +
>> > + SAFE_WAITPID(pid, &status, 0);
>> > + if (WEXITSTATUS(status) != 0) {
>> > + tst_res(TFAIL, "Child failed: %d", WEXITSTATUS(status));
>> > + goto cleanup;
>> > + }
>>
>> This can be replaced with tst_reap_children();
> Ok. I will update it in v2.
>>
>> > +
>> > + tst_res(TINFO, "child_readback = 0x%x, parent_readback = 0x%x",
>> > + *child_readback, parent_readback);
>> > +
>> > + if (*child_readback != RANDOM_CONSTANT) {
>> > + tst_res(TFAIL, "Child read back 0x%x instead of 0x%x",
>> > + *child_readback, RANDOM_CONSTANT);
>>
>> I think this could be checked at the end of the child and the extra mmap
>> for child_readback removed. The LTP lib already creats some shared
>> memory with children to propagate results.
>>
>> Assuming that mmap is not needed for the original bug reproducer.
>>
> Looking at the fix: 86df86424939d316 ("Correct hash flushing from huge_ptep_set_wrprotect()")
> seems it can be done. I will look at it and will update it in v2.
Thanks and as you have the git commit hash, please add this to the tst_test.tags.
>> > + goto cleanup;
>>
>> I don't think this is necessary.
>>
>> > + }
>> > + if (parent_readback != ~RANDOM_CONSTANT) {
>>
>> These comparisons could be replaced with TST_EXP_EQ_LU or TST_EXP_EXPR.
>>
> Ok. Will update it.
>> --
>> Thank you,
>> Richard.
>>
>> --
>> Mailing list info: https://lists.linux.it/listinfo/ltp
--
Thank you,
Richard.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-12-08 8:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 12:28 [LTP] [PATCH 0/8][PART 3] Hugetlb:Migrating the libhugetlbfs tests Tarun Sahu
2022-12-01 12:28 ` [LTP] [PATCH 1/8] Hugetlb: Migrating libhugetlbfs fork-cow Tarun Sahu
2022-12-05 12:28 ` Richard Palethorpe
2022-12-07 12:47 ` Tarun Sahu
2022-12-08 8:54 ` Richard Palethorpe [this message]
2022-12-01 12:28 ` [LTP] [PATCH 2/8] Hugetlb: Migrating libhugetlbfs huge_at_4GB_normal_below Tarun Sahu
2022-12-05 13:32 ` Richard Palethorpe
2022-12-07 12:54 ` Tarun Sahu
2022-12-01 12:28 ` [LTP] [PATCH 3/8] Hugetlb: Migrating libhugetlbfs huge_below_4GB_normal_above Tarun Sahu
2022-12-06 8:57 ` Richard Palethorpe
2022-12-07 12:51 ` Tarun Sahu
2022-12-01 12:28 ` [LTP] [PATCH 4/8] Hugetlb: Migrating libhugetlbfs icache-hygiene Tarun Sahu
2022-12-12 14:08 ` Richard Palethorpe
2022-12-13 17:27 ` Tarun Sahu
2022-12-19 21:01 ` Tarun Sahu
2022-12-01 12:28 ` [LTP] [PATCH 5/8] Hugetlb: Migrating libhugetlbfs madvise_reserve Tarun Sahu
2022-12-12 14:22 ` Richard Palethorpe
2022-12-01 12:28 ` [LTP] [PATCH 6/8] Hugetlb: Migrating libhugetlbfs map_high_truncate_2 Tarun Sahu
2022-12-12 14:26 ` Richard Palethorpe
2022-12-01 12:28 ` [LTP] [PATCH 7/8] Hugetlb: Migrating libhugetlbfs misalign Tarun Sahu
2022-12-12 14:32 ` Richard Palethorpe
2022-12-01 12:28 ` [LTP] [PATCH 8/8] Hugetlb: Migrating libhugetlbfs misaligned_offset Tarun Sahu
2022-12-12 14:33 ` Richard Palethorpe
2022-12-12 14:50 ` [LTP] [PATCH 0/8][PART 3] Hugetlb:Migrating the libhugetlbfs tests Richard Palethorpe
2022-12-13 5:00 ` Tarun Sahu
-- strict thread matches above, loose matches on Subject: below --
2022-11-20 19:15 [LTP] [PATCH v5 0/7][PART 2] " Tarun Sahu
2022-12-01 12:02 ` [LTP] [PATCH 0/8][PART 3] " Tarun Sahu
2022-12-01 12:02 ` [LTP] [PATCH 1/8] Hugetlb: Migrating libhugetlbfs fork-cow Tarun Sahu
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=87sfhqqnpo.fsf@suse.de \
--to=rpalethorpe@suse.de \
--cc=aneesh.kumar@linux.ibm.com \
--cc=geetika@linux.ibm.com \
--cc=ltp@lists.linux.it \
--cc=sbhat@linux.ibm.com \
--cc=tsahu@linux.ibm.com \
--cc=vaibhav@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