From: Andreas Dilger <adilger@dilger.ca>
To: Ayush Ranjan <ayushr2@illinois.edu>
Cc: Theodore Ts'o <tytso@mit.edu>, Jonathan Corbet <corbet@lwn.net>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
linux-doc@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Ext4 documentation fixes.
Date: Thu, 15 Aug 2019 00:09:27 -0600 [thread overview]
Message-ID: <1FBF4302-FA3E-49BE-B9AA-F380518AB263@dilger.ca> (raw)
In-Reply-To: <CA+UE=SNWDBGuFpS9Y7g5iurJEJX41c+LMwis3ZGotbJ=DSSaJA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
On Aug 14, 2019, at 6:47 PM, Ayush Ranjan <ayushr2@illinois.edu> wrote:
> diff --git a/Documentation/filesystems/ext4/inodes.rst b/Documentation/filesystems/ext4/inodes.rst
> index 6bd35e506..c468a3171 100644
> --- a/Documentation/filesystems/ext4/inodes.rst
> +++ b/Documentation/filesystems/ext4/inodes.rst
> @@ -470,8 +470,8 @@ inode, which allows struct ext4\_inode to grow for a new kernel without
> having to upgrade all of the on-disk inodes. Access to fields beyond
> EXT2\_GOOD\_OLD\_INODE\_SIZE should be verified to be within
> ``i_extra_isize``. By default, ext4 inode records are 256 bytes, and (as
> -of October 2013) the inode structure is 156 bytes
> -(``i_extra_isize = 28``). The extra space between the end of the inode
> +of October 2013) the inode structure is 160 bytes
This should be changed to "as of August 2019", or possibly the date on
which the last field (i_projid) was added, namely "October, 2015".
Cheers, Andreas
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 873 bytes --]
parent reply other threads:[~2019-08-15 6:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CA+UE=SNWDBGuFpS9Y7g5iurJEJX41c+LMwis3ZGotbJ=DSSaJA@mail.gmail.com>]
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=1FBF4302-FA3E-49BE-B9AA-F380518AB263@dilger.ca \
--to=adilger@dilger.ca \
--cc=ayushr2@illinois.edu \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).