From: Ralph Siemsen <ralph.siemsen@linaro.org>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [RFC PATCH] fallocate05: increase the fallocate and defallocate size
Date: Tue, 21 Sep 2021 16:33:49 -0400 [thread overview]
Message-ID: <20210921203349.GA2014441@maple.netwinder.org> (raw)
In-Reply-To: <20210817104625.2559362-1-liwang@redhat.com>
Hello,
On Tue, Aug 17, 2021 at 06:46:25PM +0800, Li Wang wrote:
>
>diff --git a/testcases/kernel/syscalls/fallocate/fallocate05.c b/testcases/kernel/syscalls/fallocate/fallocate05.c
>index 55ec1aee4..74bfa4861 100644
>--- a/testcases/kernel/syscalls/fallocate/fallocate05.c
>+++ b/testcases/kernel/syscalls/fallocate/fallocate05.c
>@@ -26,8 +26,8 @@
> #include "lapi/fallocate.h"
>
> #define MNTPOINT "mntpoint"
>-#define FALLOCATE_BLOCKS 16
>-#define DEALLOCATE_BLOCKS 4
>+#define FALLOCATE_BLOCKS 256
>+#define DEALLOCATE_BLOCKS 64
> #define TESTED_FLAGS "fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE)"
>
> static char *buf;
This change appears seems to be causing fallocate05 test to reliably
trigger OOM (out of memory) on my test machine, which has only 256MB
RAM.
I previously used the 20210524 and 20200120 release versions, and did
not encounter this problem.
Regards,
Ralph
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2021-09-21 20:34 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 10:46 [LTP] [RFC PATCH] fallocate05: increase the fallocate and defallocate size Li Wang
2021-09-07 2:40 ` Li Wang
2021-09-07 2:40 ` Li Wang
2021-09-07 8:00 ` Jan Stancek
2021-09-07 8:00 ` Jan Stancek
2021-09-08 1:21 ` Li Wang
2021-09-08 1:21 ` Li Wang
2021-09-21 20:33 ` Ralph Siemsen [this message]
2021-09-22 5:03 ` Li Wang
2021-09-22 8:21 ` Cyril Hrubis
2021-09-22 9:53 ` Li Wang
2021-09-22 9:56 ` Cyril Hrubis
2021-09-22 10:34 ` Li Wang
2021-09-22 14:32 ` Cyril Hrubis
2021-09-22 16:52 ` Ralph Siemsen
2021-09-23 3:00 ` Li Wang
2021-09-23 6:29 ` Li Wang
2021-09-23 13:09 ` Cyril Hrubis
2021-09-24 4:27 ` Li Wang
2021-09-23 14:33 ` Cyril Hrubis
2021-09-24 1:49 ` Ralph Siemsen
2021-09-24 4:18 ` Li Wang
2021-09-24 15:11 ` Ralph Siemsen
2021-09-24 18:26 ` Cyril Hrubis
2021-09-24 20:26 ` Ralph Siemsen
2021-09-25 2:16 ` Ralph Siemsen
2021-09-26 7:17 ` Li Wang
2021-09-26 7:40 ` Li Wang
2021-09-26 7:39 ` Li Wang
2021-09-27 1:37 ` Ralph Siemsen
2021-09-24 6:49 ` Li Wang
2021-09-24 9:33 ` Cyril Hrubis
2021-09-23 6:39 ` Li Wang
2021-09-23 13:10 ` Cyril Hrubis
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=20210921203349.GA2014441@maple.netwinder.org \
--to=ralph.siemsen@linaro.org \
--cc=liwang@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