From: "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: write/write/fallocate quota leakage
Date: Fri, 04 Jun 2010 14:33:06 +0530 [thread overview]
Message-ID: <87ljavtbjp.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <87typk1q8i.fsf@openvz.org>
On Thu, 03 Jun 2010 12:21:01 +0400, Dmitry Monakhov <dmonakhov@openvz.org> wrote:
> Recently one "write vs fallocate" quota leakage was fixed, but
> not completely. It is still possible if uninitialized extent which
> covers several delay allocated regions converted to initialized one.
>
> Take a look at test-case attached.
> The issue is clear enough, but I don't have a good solution for now.
> Off course we can add one more restriction to zeroout logic, but this is
> unproductive way because we have to keep zeroout logic simple as possible.
>
> Aneesh, do you have any sound ideas?
>
I will have to look at this more closer. Will get back to you.
-aneesh
prev parent reply other threads:[~2010-06-04 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 8:21 write/write/fallocate quota leakage Dmitry Monakhov
2010-06-04 9:03 ` Aneesh Kumar K. V [this message]
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=87ljavtbjp.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=dmonakhov@openvz.org \
--cc=linux-ext4@vger.kernel.org \
/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).