From: Christian Brauner <brauner@kernel.org>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: viro@zeniv.linux.org.uk, jack@suse.cz,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v4 1/3] vfs: add initial support for CONFIG_DEBUG_VFS
Date: Mon, 10 Feb 2025 09:28:56 +0100 [thread overview]
Message-ID: <20250210-umgibt-vorhof-5d2eb09918e2@brauner> (raw)
In-Reply-To: <20250209185523.745956-2-mjguzik@gmail.com>
On Sun, Feb 09, 2025 at 07:55:20PM +0100, Mateusz Guzik wrote:
> Small collection of macros taken from mmdebug.h
>
> Signed-off-by: Mateusz Guzik <mjguzik@gmail.com>
> ---
> fs/inode.c | 15 ++++++++++++++
> include/linux/fs.h | 1 +
> include/linux/vfsdebug.h | 45 ++++++++++++++++++++++++++++++++++++++++
> lib/Kconfig.debug | 9 ++++++++
> 4 files changed, 70 insertions(+)
> create mode 100644 include/linux/vfsdebug.h
>
> diff --git a/fs/inode.c b/fs/inode.c
> index 5587aabdaa5e..875e66261f06 100644
> --- a/fs/inode.c
> +++ b/fs/inode.c
> @@ -2953,3 +2953,18 @@ umode_t mode_strip_sgid(struct mnt_idmap *idmap,
> return mode & ~S_ISGID;
> }
> EXPORT_SYMBOL(mode_strip_sgid);
> +
> +#ifdef CONFIG_DEBUG_VFS
> +/*
> + * Dump an inode.
> + *
> + * TODO: add a proper inode dumping routine, this is a stub to get debug off the
> + * ground.
> + */
> +void dump_inode(struct inode *inode, const char *reason)
> +{
> + pr_warn("%s encountered for inode %px", reason, inode);
I had already fixed that in the local tree. But thanks for resending.
I'll take v4 then.
next prev parent reply other threads:[~2025-02-10 8:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-09 18:55 [PATCH v4 0/3] CONFIG_DEBUG_VFS at last Mateusz Guzik
2025-02-09 18:55 ` [PATCH v4 1/3] vfs: add initial support for CONFIG_DEBUG_VFS Mateusz Guzik
2025-02-10 8:28 ` Christian Brauner [this message]
2025-02-09 18:55 ` [PATCH v4 2/3] vfs: catch invalid modes in may_open() Mateusz Guzik
2025-02-09 18:55 ` [PATCH v4 3/3] vfs: use the new debug macros in inode_set_cached_link() Mateusz Guzik
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=20250210-umgibt-vorhof-5d2eb09918e2@brauner \
--to=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjguzik@gmail.com \
--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
all inboxes | Powered by JetHome®