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] fs: expand dump_inode()
Date: Mon, 15 Sep 2025 14:15:44 +0200 [thread overview]
Message-ID: <20250915-meilenstein-simulation-7e220d91b339@brauner> (raw)
In-Reply-To: <20250909082613.1296550-1-mjguzik@gmail.com>
On Tue, Sep 09, 2025 at 10:26:13AM +0200, Mateusz Guzik wrote:
> This adds fs name and few fields from struct inode: i_mode, i_opflags,
> i_flags and i_state.
>
> All values printed raw, no attempt to pretty-print anything.
>
> Compile tested on for i386 and runtime tested on amd64.
>
> Sample output:
> [ 31.450263] VFS_WARN_ON_INODE("crap") encountered for inode ffff9b10837a3240
> fs sockfs mode 140777 opflags c flags 0 state 100
>
> Signed-off-by: Mateusz Guzik <mjguzik@gmail.com>
> ---
Applied to vfs-6.18.misc.
next prev parent reply other threads:[~2025-09-15 12:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 8:26 [PATCH] fs: expand dump_inode() Mateusz Guzik
2025-09-15 12:15 ` Christian Brauner [this message]
2025-09-15 12:17 ` Mateusz Guzik
2025-09-15 13:42 ` 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=20250915-meilenstein-simulation-7e220d91b339@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