From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Samir Mulani" <samir@linux.ibm.com>, <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] [PATCH v4] Migrating the libhugetlbfs/testcases/truncate_sigbus_versus_oom.c test
Date: Tue, 17 Feb 2026 15:23:23 +0100 [thread overview]
Message-ID: <DGHAZKT0BPBL.167V6DLGZOOF@suse.com> (raw)
In-Reply-To: <20250928034647.3539824-1-samir@linux.ibm.com>
Hi!
On Sun Sep 28, 2025 at 5:46 AM CEST, Samir Mulani wrote:
> In this test case, we are verifying the bug fix commit that is attached as
> a part of the test case structure,
>
> Some kernel have a bug in the positioning of the test against
^
typo: kernels
> +++ b/testcases/kernel/mem/hugetlb/hugemmap/hugemmap37.c
> @@ -0,0 +1,94 @@
> +// SPDX-License-Identifier: GPL-2.0-or-later
> +/*
> + * Copyright (C) 2005-2006 David Gibson & Adam Litke, IBM Corporation.
> + */
> +
> +/*\
> + * [Description]
Description is not needed anymore.
> + *
> + * Some kernel have a bug in the positioning of the test against
^
typo: kernels
> + * i_size. This bug means that attempting to instantiate a page
> + * beyond the end of a hugepage file can result in an OOM and SIGKILL
> + * instead of the correct SIGBUS.
> + */
> +
> +#include "hugetlb.h"
> +#include <setjmp.h>
> +#include <signal.h>
> +
> +#define MNTPOINT "hugetlbfs/"
> +static int fd = -1, fdx = -1;
> +
> +static unsigned long long hpage_size;
> +static unsigned long totpages;
> +struct sigaction sa;
Should be used inside the setup().
> +static sigjmp_buf sig_escape;
> +static volatile int test_pass;
> +static int sigbus_count;
Never used.
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-02-17 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 3:46 [LTP] [PATCH] [PATCH v4] Migrating the libhugetlbfs/testcases/truncate_sigbus_versus_oom.c test Samir Mulani
2026-02-17 14:23 ` Andrea Cervesato via ltp [this message]
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=DGHAZKT0BPBL.167V6DLGZOOF@suse.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=samir@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