From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 1/6] GFS2: quotas not being refreshed in gfs2_adjust_quota
Date: Tue, 3 Jun 2014 12:02:28 +0100 [thread overview]
Message-ID: <1401793353-1469-2-git-send-email-swhiteho@redhat.com> (raw)
In-Reply-To: <1401793353-1469-1-git-send-email-swhiteho@redhat.com>
From: Abhi Das <adas@redhat.com>
Old values of user quota limits were being used and
could allow users to exceed their allotted quotas.
This patch refreshes the limits to the latest values
so that quotas are enforced correctly.
Resolves: rhbz#1077463
Signed-off-by: Abhi Das <adas@redhat.com>
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
diff --git a/fs/gfs2/quota.c b/fs/gfs2/quota.c
index c4effff..6193896 100644
--- a/fs/gfs2/quota.c
+++ b/fs/gfs2/quota.c
@@ -778,6 +778,7 @@ get_a_page:
i_size_write(inode, size);
inode->i_mtime = inode->i_atime = CURRENT_TIME;
mark_inode_dirty(inode);
+ set_bit(QDF_REFRESH, &qd->qd_flags);
return 0;
unlock_out:
--
1.8.3.1
next prev parent reply other threads:[~2014-06-03 11:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 11:02 [Cluster-devel] GFS2: Pre-pull patch posting (merge window) Steven Whitehouse
2014-06-03 11:02 ` Steven Whitehouse [this message]
2014-06-03 11:02 ` [Cluster-devel] [PATCH 2/6] GFS2: lops.c: replace 0 by NULL for pointers Steven Whitehouse
2014-06-03 11:02 ` [Cluster-devel] [PATCH 3/6] GFS2: remove transaction glock Steven Whitehouse
2014-06-03 11:02 ` [Cluster-devel] [PATCH 4/6] GFS2: fs/gfs2/bmap.c: kernel-doc warning fixes Steven Whitehouse
2014-06-03 11:02 ` [Cluster-devel] [PATCH 5/6] GFS2: fs/gfs2/file.c: " Steven Whitehouse
2014-06-03 11:02 ` [Cluster-devel] [PATCH 6/6] GFS2: Prevent recovery before the local journal is set 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=1401793353-1469-2-git-send-email-swhiteho@redhat.com \
--to=swhiteho@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).