[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aMJkIbDwuzJkH53b@dread.disaster.area>
Date: Thu, 11 Sep 2025 15:54:41 +1000
From: Dave Chinner <david@...morbit.com>
To: Mateusz Guzik <mjguzik@...il.com>
Cc: brauner@...nel.org, viro@...iv.linux.org.uk, jack@...e.cz,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
josef@...icpanda.com, kernel-team@...com, amir73il@...il.com,
linux-btrfs@...r.kernel.org, linux-ext4@...r.kernel.org,
linux-xfs@...r.kernel.org, ocfs2-devel@...ts.linux.dev
Subject: Re: [PATCH v3 1/4] fs: expand dump_inode()
On Thu, Sep 11, 2025 at 06:55:54AM +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.
Please use '0x' prefixes for hexadecimal output.....
>
> 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
.... because reading this I have no idea if "state 100" means a
value of one hundred, 0x100 (i.e. 256 decimal), or something else
entirely. I have to go look at the code to work it out, then I have
to remember that every time I look at one of these lines of output.
When I'm looking through gigabytes of debug output, it's little
things like this make a big difference to how quickly I can read the
important information in the output...
Otherwise it's ok, though I would have added the reference count
for the inode as well...
-Dave.
--
Dave Chinner
david@...morbit.com
Powered by blists - more mailing lists