From: Mateusz Guzik <mjguzik@gmail.com>
To: brauner@kernel.org
Cc: viro@zeniv.linux.org.uk, jack@suse.cz,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Mateusz Guzik <mjguzik@gmail.com>
Subject: [PATCH 0/3] CONFIG_VFS_DEBUG at last
Date: Wed, 5 Feb 2025 19:38:36 +0100 [thread overview]
Message-ID: <20250205183839.395081-1-mjguzik@gmail.com> (raw)
This adds a super basic version just to get the mechanism going and
adds sample usage.
The macro set is incomplete (e.g., lack of locking macros) and
dump_inode routine fails to dump any state yet, to be implemented(tm).
I think despite the primitive state this is complete enough to start
sprinkling warns as necessary.
Mateusz Guzik (3):
vfs: add initial support for CONFIG_VFS_DEBUG
vfs: catch invalid modes in may_open
vfs: use the new debug macros in inode_set_cached_link()
fs/namei.c | 2 ++
include/linux/fs.h | 16 +++----------
include/linux/vfsdebug.h | 50 ++++++++++++++++++++++++++++++++++++++++
lib/Kconfig.debug | 9 ++++++++
4 files changed, 64 insertions(+), 13 deletions(-)
create mode 100644 include/linux/vfsdebug.h
--
2.43.0
next reply other threads:[~2025-02-05 18:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 18:38 Mateusz Guzik [this message]
2025-02-05 18:38 ` [PATCH 1/3] vfs: add initial support for CONFIG_VFS_DEBUG Mateusz Guzik
2025-02-05 18:38 ` [PATCH 2/3] vfs: catch invalid modes in may_open Mateusz Guzik
2025-02-05 18:38 ` [PATCH 3/3] vfs: use the new debug macros in inode_set_cached_link() Mateusz Guzik
2025-02-05 18:57 ` [PATCH 0/3] CONFIG_VFS_DEBUG at last Mateusz Guzik
2025-02-06 9:46 ` Christian Brauner
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=20250205183839.395081-1-mjguzik@gmail.com \
--to=mjguzik@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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