From: Cyril Hrubis <chrubis@suse.cz>
To: Victor Cheng-Yen Yang <cyyang772@andestech.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] mmap21: Check for free space before mapping the file
Date: Tue, 8 Sep 2026 12:47:35 +0200 [thread overview]
Message-ID: <ap_nx7AZvluXzW-i@yuki.lan> (raw)
In-Reply-To: <20260908023121.1895897-1-cyyang772@andestech.com>
Hi!
> The test creates a sparse file with lseek() and a one byte write, so
> mmap() allocates no blocks. The child then touches every byte and ext4
> fills the holes inside ext4_page_mkwrite(). A store instruction has no
> error return, so an ENOSPC there becomes VM_FAULT_SIGBUS and the test
> reports only
>
> tst_test.c:536: TBROK: Child (13042) killed by signal SIGBUS
>
> which says nothing about the full filesystem. The information is
> available before the mapping and gone after it, so check it in setup
> and report TCONF earlier as convention.
Depending on the page size this is either 4MB or 64MB, I would say that
if you run LTP on a machine with less than 4MB of free space many tests
would fail.
Maybe it would make sense to print a warning from the test library for
any tests that has needs_tmpdir == 1 and the free space at the test
temporary directory is less than a few megabytes.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-09-08 10:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 2:31 [LTP] [PATCH] mmap21: Check for free space before mapping the file Victor Cheng-Yen Yang via ltp
2026-09-08 5:41 ` [LTP] " linuxtestproject.agent
2026-09-08 10:47 ` Cyril Hrubis [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=ap_nx7AZvluXzW-i@yuki.lan \
--to=chrubis@suse.cz \
--cc=cyyang772@andestech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.