From: Ben Myers <bpm@sgi.com>
To: Jeff Liu <jeff.liu@oracle.com>, Christoph Hellwig <hch@infradead.org>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: [PATCH v2 2/3] xfs: fix infinite loop by detaching the group/project hints from user dquot
Date: Fri, 6 Dec 2013 15:01:37 -0600 [thread overview]
Message-ID: <20131206210137.GT1935@sgi.com> (raw)
In-Reply-To: <52986001.9040101@oracle.com>
Hey Jeff,
On Fri, Nov 29, 2013 at 05:36:01PM +0800, Jeff Liu wrote:
> On 11/28 2013 18:43 PM, Christoph Hellwig wrote:
> > On Tue, Nov 26, 2013 at 09:38:49PM +0800, Jeff Liu wrote:
> >> + if (flags & XFS_QMOPT_UQUOTA)
> >> + return xfs_qm_dqpurge(dqp, NULL);
> >
> > To me it doesn't make any sense to overload this function for the user
> > quotas that don't have hints.
> To me it would like a silly compromise.
> >
> > I'd suggest dropping this hunk and keeping a separate walk for
> > releasing the uquots.
> I thought this over and yup, that is an overload if neither group nor project
> are enabled, or we don't want to turn user quota off.
>
> But even so, we currently also have overloads by checking group/project hints
> before releasing any type of quota in xfs_qm_purge(). In this point, this fix
> can reduce a bit overloads by moving those checkups to xfs_qm_purge_hints() if
> we want to turn group/project quotas off.
>
> If we considering to drop above hunk to release user quota separately, we finally
> would have to walk through user quota to remove those hints again, i.e,
>
> /* Remove group/project hints from user dquot */
> STATIC int
> xfs_qm_dqpurge_hints(
> struct xfs_dquot *dqp,
> void *data)
> {
> uint flags = *((uint *)data);
> struct xfs_dquot *gdqp;
> struct xfs_dquot *pdqp;
>
> xfs_dqlock(dqp);
> if (dqp->dq_flags & XFS_DQ_FREEING) {
> xfs_dqunlock(dqp);
> return EAGAIN;
> }
>
> /* If this quota has a hint attached, prepare for releasing it now */
> gdqp = dqp->q_gdquot;
> if (gdqp)
> dqp->q_gdquot = NULL;
>
> pdqp = dqp->q_pdquot;
> if (pdqp)
> dqp->q_pdquot = NULL;
>
> xfs_dqunlock(dqp);
>
> if (gdqp)
> xfs_qm_dqrele(gdqp);
> if (pdqp)
> xfs_qm_dqrele(pdqp);
>
> return 0;
> }
>
> void
> xfs_qm_dqpurge_all()
> {
> xfs_qm_dquot_walk(mp, XFS_DQ_USER, xfs_qm_dqpurge_hints, NULL);
>
> if (flags & XFS_QMOPT_UQUOTA)
> xfs_qm_dquot_walk(mp, XFS_DQ_USER, xfs_qm_dqpurge, NULL);
> if (flags & XFS_QMOPT_GQUOTA)
> xfs_qm_dquot_walk(mp, XFS_DQ_GROUP, xfs_qm_dqpurge, NULL);
> if (flags & XFS_QMOPT_PQUOTA)
> xfs_qm_dquot_walk(mp, XFS_DQ_PROJ, xfs_qm_dqpurge, NULL);
> }
>
> Above code is what I can figured out as per your suggestions for now, but it
> would introduce overheads for walking through user dquots to release hints
> separately if we want to turn user quota off.
>
> Any thoughts?
I was gonna pull in the single walk version, but now I realize that it is still
under discussion. I'm happy with either implementation, with maybe a slight
preference for a single user quota walk. Can you and Christoph come to an
agreement?
Thanks,
Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-12-06 21:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 13:38 [PATCH v2 2/3] xfs: fix infinite loop by detaching the group/project hints from user dquot Jeff Liu
2013-11-28 10:43 ` Christoph Hellwig
2013-11-29 9:36 ` Jeff Liu
2013-12-06 21:01 ` Ben Myers [this message]
2013-12-07 5:51 ` Jeff Liu
2013-12-09 1:26 ` Dave Chinner
2013-12-09 2:36 ` Dave Chinner
2013-12-09 3:26 ` Jeff Liu
2013-12-09 6:09 ` Dave Chinner
2013-12-09 6:36 ` Dave Chinner
2013-12-09 7:10 ` Christoph Hellwig
2013-12-09 23:07 ` Ben Myers
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=20131206210137.GT1935@sgi.com \
--to=bpm@sgi.com \
--cc=hch@infradead.org \
--cc=jeff.liu@oracle.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