public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chandan Babu R <chandan.babu@oracle.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: darrick.wong@oracle.com, linux-xfs@vger.kernel.org,
	allison.henderson@oracle.com
Subject: Re: [PATCH 1/3] design: update group quota inode information for v5 filesystems
Date: Tue, 24 Jan 2023 10:59:32 +0530	[thread overview]
Message-ID: <87cz74lct9.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <167400163292.1925795.12938763753506074554.stgit@magnolia>

On Tue, Jan 17, 2023 at 04:44:49 PM -0800, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> Fix a few out of date statements about the group quota inode field on v5
> filesystems.
>

Looks good to me.

Reviewed-by: Chandan Babu R <chandan.babu@oracle.com>

-- 
chandan

> Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> ---
>  .../allocation_groups.asciidoc                     |    7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
>
>
> diff --git a/design/XFS_Filesystem_Structure/allocation_groups.asciidoc b/design/XFS_Filesystem_Structure/allocation_groups.asciidoc
> index 0e48b4bf..7ee5d561 100644
> --- a/design/XFS_Filesystem_Structure/allocation_groups.asciidoc
> +++ b/design/XFS_Filesystem_Structure/allocation_groups.asciidoc
> @@ -262,11 +262,12 @@ maintained in the first superblock.
>  *sb_uquotino*::
>  Inode for user quotas. This and the following two quota fields only apply if
>  +XFS_SB_VERSION_QUOTABIT+ flag is set in +sb_versionnum+. Refer to
> -xref:Quota_Inodes[quota inodes] for more information
> +xref:Quota_Inodes[quota inodes] for more information.
>  
>  *sb_gquotino*::
> -Inode for group or project quotas. Group and Project quotas cannot be used at
> -the same time.
> +Inode for group or project quotas. Group and project quotas cannot be used at
> +the same time on v4 filesystems.  On a v5 filesystem, this inode always stores
> +group quota information.
>  
>  *sb_qflags*::
>  Quota flags. It can be a combination of the following flags:

  reply	other threads:[~2023-01-24  5:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18  0:42 [PATCHSET 0/3] xfs-documentation: updates for 6.1 Darrick J. Wong
2023-01-18  0:44 ` [PATCH 1/3] design: update group quota inode information for v5 filesystems Darrick J. Wong
2023-01-24  5:29   ` Chandan Babu R [this message]
2023-01-18  0:45 ` [PATCH 2/3] design: document the large extent count ondisk format changes Darrick J. Wong
2023-01-24  5:30   ` Chandan Babu R
2023-01-18  0:45 ` [PATCH 3/3] design: document extended attribute log item changes Darrick J. Wong
2023-01-24  5:30   ` Chandan Babu R
2023-01-25  1:20     ` Darrick J. Wong

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=87cz74lct9.fsf@debian-BULLSEYE-live-builder-AMD64 \
    --to=chandan.babu@oracle.com \
    --cc=allison.henderson@oracle.com \
    --cc=darrick.wong@oracle.com \
    --cc=djwong@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    /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