From: Abhijith Das <adas@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH][GFS2] bz235299: Fix quota do_list operation hang
Date: Wed, 15 Aug 2007 11:25:05 -0500 [thread overview]
Message-ID: <46C328E1.2040409@redhat.com> (raw)
This is the filesystem part of the patches to fix this bz. There are
additional userland patches (gfs2_quota, libgfs2) for the complete
solution. This patch adds a new field qu_ll_next to the gfs2_quota
structure. This field allows us to create linked lists of quotas in the
ondisk quota inode. Instead of scanning through the entire sparse quota
file for valid quotas, we can now simply walk through the user and group
quota linked lists to perform the do_list operation.
Signed-off-by: Abhijith Das <adas@redhat.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bz235299-GFS2KERNEL.patch
Type: text/x-patch
Size: 2643 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20070815/2a90b45f/attachment.bin>
next reply other threads:[~2007-08-15 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 16:25 Abhijith Das [this message]
2007-08-15 16:27 ` [Cluster-devel] Re: [PATCH][GFS2] bz235299: Fix quota do_list operation hang Steven Whitehouse
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=46C328E1.2040409@redhat.com \
--to=adas@redhat.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;
as well as URLs for NNTP newsgroup(s).