From: Abhi Das <adas@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH 0/3] fallocate quota fixes
Date: Mon, 16 Feb 2015 11:59:40 -0600 [thread overview]
Message-ID: <1424109583-42670-1-git-send-email-adas@redhat.com> (raw)
This is a revised set of patches for bz1174295 to address
fallocate/quota issues. These patches are only compile
tested so far.
patch 1 - This is the patch that actually addresses the quota
exceed issue. Quota checks were not being performed
against the blocks about to be allocated.
patch 2 - Modify gfs2_inplace_reserve() and gfs2_quota_check()
to return available number of blocks in case of
failure.
patch 3 - Allows fallocate to take advantage of patch 2 to
efficiently max out quotas or fill up the fs instead
of returning -EDQUOT/-ENOSPC and leaving some
available blocks unallocated.
Abhi Das (3):
gfs2: perform quota checks against allocation parameters
gfs2: allow quota_check and inplace_reserve to return available blocks
gfs2: allow fallocate to max out quotas/fs efficiently
fs/gfs2/aops.c | 6 +++---
fs/gfs2/bmap.c | 2 +-
fs/gfs2/file.c | 27 ++++++++++++++++-----------
fs/gfs2/incore.h | 3 ++-
fs/gfs2/inode.c | 18 ++++++++++--------
fs/gfs2/quota.c | 21 ++++++++++++++++++---
fs/gfs2/quota.h | 8 +++++---
fs/gfs2/rgrp.c | 8 +++++++-
fs/gfs2/rgrp.h | 2 +-
fs/gfs2/xattr.c | 2 +-
10 files changed, 64 insertions(+), 33 deletions(-)
--
1.8.1.4
next reply other threads:[~2015-02-16 17:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 17:59 Abhi Das [this message]
2015-02-16 17:59 ` [Cluster-devel] [GFS2 PATCH 1/3] gfs2: perform quota checks against allocation parameters Abhi Das
2015-02-17 9:38 ` Steven Whitehouse
2015-02-17 15:00 ` Abhijith Das
2015-02-16 17:59 ` [Cluster-devel] [GFS2 PATCH 2/3] gfs2: allow quota_check and inplace_reserve to return available blocks Abhi Das
2015-02-16 17:59 ` [Cluster-devel] [GFS2 PATCH 3/3] gfs2: allow fallocate to max out quotas/fs efficiently Abhi Das
2015-02-17 9:41 ` Steven Whitehouse
2015-02-17 15:07 ` Abhijith Das
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=1424109583-42670-1-git-send-email-adas@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).