Linux Test Project
 help / color / mirror / Atom feed
From: Li Wang <liwang@redhat.com>
To: ltp@lists.linux.it
Cc: Luis Goncalves <lgoncalv@redhat.com>
Subject: [LTP] [PATCH] madvise11: ignore EBUSY for MADV_SOFT_OFFLINE
Date: Thu,  9 May 2024 18:28:02 +0800	[thread overview]
Message-ID: <20240509102802.20091-1-liwang@redhat.com> (raw)

The EBUSY error could be easily triggered on small system with
kernel-debug. By not treating EBUSY as a failure, the test can
avoid false positives where the test environment itself might
frequently cause resource contention.

Test output:
  madvise11.c:409: TINFO: Spawning 4 threads, with a total of 640 memory pages
  madvise11.c:163: TINFO: Thread [0] returned 0, succeeded.
  madvise11.c:163: TINFO: Thread [2] returned 0, succeeded.
  madvise11.c:163: TINFO: Thread [1] returned 0, succeeded.
  madvise11.c:163: TINFO: Thread [3] returned 0, succeeded.
  madvise11.c:198: TPASS: soft-offline / mmap race still clean     <--- end of 1st test
  madvise11.c:132: TFAIL: madvise failed: EBUSY (16)               <--- ERROR!
  ...

From kernel log:
  [ 431.590511] soft offline: 0xbfa8f: page migration failed 1, type
  0x800000008002e(referenced|uptodate|dirty|active|swapbacked|node=0|zone=1)
  ...
  [ 435.510819] soft offline: 0x98fb6: page migration failed 1, type
  0x800000008000e(referenced|uptodate|dirty|swapbacked|node=0|zone=1)
  ...

Kernel callpath:
  do_madvise()
  ---
  #ifdef CONFIG_MEMORY_FAILURE
      if (behavior == MADV_HWPOISON || behavior == MADV_SOFT_OFFLINE)
          return madvise_inject_error(behavior, start, start + len_in);
  #endif
  ---
    madvise_inject_error()
      soft_offline_page()
        soft_offline_in_use_page()
 	  ...
           2727	pr_info("soft offline: %#lx: %s migration failed %ld, type %pGp\n",
           2728		pfn, msg_page[huge], ret, &page->flags);
           2729	if (ret > 0)
           2730		ret = -EBUSY;   <--- Here

Debugged-by: Luis Goncalves <lgoncalv@redhat.com>
Signed-off-by: Li Wang <liwang@redhat.com>
---
 testcases/kernel/syscalls/madvise/madvise11.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/testcases/kernel/syscalls/madvise/madvise11.c b/testcases/kernel/syscalls/madvise/madvise11.c
index 7a12abf20..fe27a18d8 100644
--- a/testcases/kernel/syscalls/madvise/madvise11.c
+++ b/testcases/kernel/syscalls/madvise/madvise11.c
@@ -128,6 +128,8 @@ static int allocate_offline(int tnum)
 				return -1;
 
 			if (madvise(ptrs[num_alloc], pagesize, MADV_SOFT_OFFLINE) == -1) {
+				if (errno == EBUSY)
+					continue;
 				if (errno != EINVAL)
 					tst_res(TFAIL | TERRNO, "madvise failed");
 				if (errno == EINVAL)
-- 
2.45.0


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

             reply	other threads:[~2024-05-09 10:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-09 10:28 Li Wang [this message]
2024-05-09 13:40 ` [LTP] [PATCH] madvise11: ignore EBUSY for MADV_SOFT_OFFLINE Petr Vorel
2024-05-10  2:36   ` Li Wang

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=20240509102802.20091-1-liwang@redhat.com \
    --to=liwang@redhat.com \
    --cc=lgoncalv@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