From: Abhijith Das <adas@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] - Bug 675745 - GFS2: panics on quotacheck update
Date: Mon, 7 Feb 2011 11:22:41 -0500 (EST) [thread overview]
Message-ID: <692347302.51330.1297095761673.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <1310979454.51316.1297095727127.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
Handle block allocation for forceful unstuffing of quota dinode during quota update using quotactl(). Also fix block reservation for special cases when quotas cross over block boundaries and update 2 blocks instead of 1.
Resolves: rhbz#675745
Signed-off-by: Abhi Das <adas@redhat.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bz675745-upstream.patch
Type: text/x-patch
Size: 873 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20110207/52c51f2e/attachment.bin>
next parent reply other threads:[~2011-02-07 16:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1310979454.51316.1297095727127.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2011-02-07 16:22 ` Abhijith Das [this message]
2011-02-07 20:26 ` [Cluster-devel] [GFS2 PATCH] - Bug 675745 - GFS2: panics on quotacheck update 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=692347302.51330.1297095761673.JavaMail.root@zmail05.collab.prod.int.phx2.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).