From: Chandra Seetharaman <sekharan@us.ibm.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH v7 0/5] xfs: Allow pquota and gquota to be used together
Date: Fri, 22 Mar 2013 10:00:46 -0500 [thread overview]
Message-ID: <1363964446.27672.14.camel@chandra-dt.ibm.com> (raw)
In-Reply-To: <20130322020243.GR17758@dastard>
Sure. I will look at your CRC patchset and see what changes are needed
to mine.
Meantime, you can answer my dilemma with the change in fs_quota_stat
(see patch 4).
As per your suggestion, I changed the data structure, to include pads at
relevant places in the data structure, which also means that the new
modified structure is not compatible with older user space code.
So, I created a copy of the older structure (fs_quota_stat_v1) and used
that if the user space request has older structure. So, now the new
kernel code is backward compatible with the old (already running) user
space code. All is well till now....
Now, I make the changes to the user space code so as to use the new
fs_quota_stat. Since the data structure has changed, the new user space
code will not work with the old kernel code.
This is where I have the dilemma.
1. Leave the user space code to work only with the newer version,
breaking the compatibility with the older kernel (with an error
message).
or
2. Read the superblock, and if pquotino is _not_ present conclude older
version of fs_quota_stat would suffice for getting quota information
from kernel (note that this will work properly with newer kernel code
too), and use the older version of fs_quota_stat_v1 for quotactl.
or
3. Any other clever way ? :)
Regards,
Chandra
On Fri, 2013-03-22 at 13:02 +1100, Dave Chinner wrote:
> On Thu, Mar 21, 2013 at 04:52:49PM -0500, Chandra Seetharaman wrote:
> > Hello All,
> >
> > This is the version 7 of the changes to allow pquota and gquota to be used
> > together.
> >
> > Patchset applies cleanly on top of 56cea2d088811b8cf7d2893e29bcf369a912de69
> > in xfs git tree.
> >
> > Ran latest xfstests against it.
>
> As an information point - I've got a separate pquota inode in the
> version 5 superblock format used in the CRC patchset. Given that
> this functionailty requires mkfs/db/repair support, woul dit be
> better to wait until the CRC code goes in and we can then add this
> feature without having to rework the superblock CRC patches around
> it?
>
> i.e. it will always be available on v5 superblocks, or v4
> superblocks when the feature bit is set to indicate the pquota inode
> part of the superblock is valid?
>
> Cheers,
>
> Dave.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-03-22 15:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 21:52 [PATCH v7 0/5] xfs: Allow pquota and gquota to be used together Chandra Seetharaman
2013-03-21 21:52 ` [PATCH v7 1/5] xfs: Remove incore use of XFS_OQUOTA_ENFD and XFS_OQUOTA_CHKD Chandra Seetharaman
2013-03-21 21:52 ` [PATCH v7 2/5] xfs: Add pquota fields and use them at appropriate places Chandra Seetharaman
2013-03-21 21:52 ` [PATCH v7 3/5] xfs: Add pquotaino to on-disk super block Chandra Seetharaman
2013-03-21 21:52 ` [PATCH v7 4/5] xfs: Add proper versioning support to fs_quota_stat Chandra Seetharaman
2013-03-21 21:52 ` [PATCH v7 5/5] xfs: Use the new qs_pquota field in fs_quota_stat for Q_XGETQSTAT Chandra Seetharaman
2013-03-22 2:02 ` [PATCH v7 0/5] xfs: Allow pquota and gquota to be used together Dave Chinner
2013-03-22 15:00 ` Chandra Seetharaman [this message]
2013-03-24 23:14 ` Dave Chinner
2013-03-25 20:08 ` Chandra Seetharaman
2013-04-29 17:28 ` Chandra Seetharaman
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=1363964446.27672.14.camel@chandra-dt.ibm.com \
--to=sekharan@us.ibm.com \
--cc=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
/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