linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@arm.com>
To: Shuah Khan <shuah@kernel.org>, Nhat Pham <nphamcs@gmail.com>,
	Johannes Weiner <hannes@cmpxchg.org>
Cc: linux-kselftest@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] selftests: cachestat: fix run on older kernels
Date: Mon, 21 Aug 2023 17:05:32 +0100	[thread overview]
Message-ID: <20230821160534.3414911-1-andre.przywara@arm.com> (raw)

I ran all kernel selftests on some test machine, and stumbled upon
cachestat failing (among others).
These patches fix the run on older kernels and when the current
directory is on a tmpfs instance.

I dropped the first two fix patches from v1, since Shuah applied those
already. [PATCH v2 1/2] is almost the same as [PATCH 3/3] from v1, but
using the proper skip function from kselftest.h. I am not sure if Shuah
applied that already, if yes, it's not a big problem, the output is the
same.

Patch 2/2 implements the tmpfs detection that Nhat suggested the last
time (many thanks for pointing me to statfs and the magics!).

Cheers,
Andre

Andre Przywara (2):
  selftests: cachestat: test for cachestat availability
  selftests: cachestat: catch failing fsync test on tmpfs

 .../selftests/cachestat/test_cachestat.c      | 80 +++++++++++++++----
 1 file changed, 65 insertions(+), 15 deletions(-)

-- 
2.25.1



             reply	other threads:[~2023-08-21 16:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-21 16:05 Andre Przywara [this message]
2023-08-21 16:05 ` [PATCH v2 1/2] selftests: cachestat: test for cachestat availability Andre Przywara
2023-08-21 16:05 ` [PATCH v2 2/2] selftests: cachestat: catch failing fsync test on tmpfs Andre Przywara
2023-08-22 15:55   ` Nhat Pham
2023-08-22 16:58     ` Nhat Pham

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=20230821160534.3414911-1-andre.przywara@arm.com \
    --to=andre.przywara@arm.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nphamcs@gmail.com \
    --cc=shuah@kernel.org \
    /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