linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Monakhov <dmonakhov@openvz.org>
To: tytso@mit.edu
Cc: "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>,
	linux-ext4@vger.kernel.org
Subject: Re: [PATCH 2/2] ext4: fix delalloc retry loop logic v2
Date: Fri, 05 Feb 2010 00:50:15 +0300	[thread overview]
Message-ID: <87636cwu08.fsf@openvz.org> (raw)
In-Reply-To: <20100204194559.GL25885@thunk.org> (tytso@mit.edu's message of "Thu, 4 Feb 2010 14:45:59 -0500")

tytso@mit.edu writes:

> Dmitry, what version were you testing when you ran into the problem
> that you reported?  Annesh's patch hit mainline just before 2.6.33-rc6.
I've hit the bug on Jan's quota tree (33-rc5 before Annesh's patch)
Yesterday i have no inet connection to check mainstream tree.
Obviously i've expected what quota-tree should contain working quota code. 
My patch is almost equals to Annesh's. So current mainstream is OK.
Sorry for false warning.
BTW. I want to deploy automated testing suite in order to test some devel
trees on daily basis in order to avoid obvious regressions (f.e. when i
broke ext3+quota). Do you know a good one?
Currently i'm looking in to autotest.kernel.org


  reply	other threads:[~2010-02-04 21:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-03 18:39 [PATCH 2/2] ext4: fix delalloc retry loop logic Dmitry Monakhov
2010-02-03 19:07 ` [PATCH 2/2] ext4: fix delalloc retry loop logic v2 Dmitry Monakhov
2010-02-03 21:16   ` tytso
2010-02-04 11:29   ` Aneesh Kumar K. V
2010-02-04 19:45     ` tytso
2010-02-04 21:50       ` Dmitry Monakhov [this message]
2010-02-05  3:55         ` tytso

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=87636cwu08.fsf@openvz.org \
    --to=dmonakhov@openvz.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).