From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>
Subject: [PATCH 0/3] selftest: preparations for devfs changes
Date: Wed, 10 Dec 2025 11:15:58 +0100 [thread overview]
Message-ID: <20251210-devfs-prep-v1-0-3a2a3aa27eab@pengutronix.de> (raw)
With the devfs series devfs as a filesystem will go away. The dirfd
selftest uses it though, so switch this test to use ramfs instead. This
revealed a bug in the fs layer which is fixed in this series.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
Sascha Hauer (3):
fs: get path in path_init()
fs: warn when mount reference count becomes negative
test: dirfs: use ramfs rather than devfs
fs/fs.c | 7 +++++++
test/self/dirfd.c | 46 +++++++++++++++++++++++++++++++++-------------
2 files changed, 40 insertions(+), 13 deletions(-)
---
base-commit: 500df27eb054f86ce232c5bb30c3a7ea8f771e61
change-id: 20251210-devfs-prep-a8909ffc695d
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
next reply other threads:[~2025-12-10 10:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 10:15 Sascha Hauer [this message]
2025-12-10 10:15 ` [PATCH 1/3] fs: get path in path_init() Sascha Hauer
2025-12-10 10:16 ` [PATCH 2/3] fs: warn when mount reference count becomes negative Sascha Hauer
2025-12-10 10:16 ` [PATCH 3/3] test: dirfs: use ramfs rather than devfs Sascha Hauer
2025-12-15 9:30 ` [PATCH 0/3] selftest: preparations for devfs changes Sascha Hauer
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=20251210-devfs-prep-v1-0-3a2a3aa27eab@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.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