From: jing zhang <zj.barak@gmail.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: tytso@mit.edu,
"Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>,
linux-ext4 <linux-ext4@vger.kernel.org>,
Andreas Dilger <adilger@sun.com>,
Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Subject: Re: [PATCH] ext4: memory leakage in ext4_mb_init()
Date: Mon, 5 Apr 2010 13:08:58 +0800 [thread overview]
Message-ID: <o2tac8f92701004042208l99c70297mf9955beacacd96bf@mail.gmail.com> (raw)
In-Reply-To: <4BB96E14.9010903@redhat.com>
2010/4/5, Eric Sandeen <sandeen@redhat.com>:
> Testing really is critical to development; some things can be done by
> inspection, but if you don't test it is hard to know if you made a
> mistake.
>
> You can always test inside a vm, or on a loopback file, on a single box.
>
> Without testing, you are asking others to do testing for you
> (unless the change is so obvious that it can be trusted)
>
Before linux-2.6.32 is released, would you like tell me, how is ext4 tested?
Is tough testing able to catch all bugs?
- zj
next prev parent reply other threads:[~2010-04-05 5:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 14:01 [PATCH] ext4: memory leakage in ext4_mb_init() jing zhang
2010-03-22 1:27 ` tytso
2010-03-23 12:47 ` jing zhang
2010-03-26 8:57 ` Aneesh Kumar K. V
2010-03-26 14:40 ` jing zhang
2010-03-28 8:13 ` jing zhang
2010-04-03 16:53 ` tytso
2010-04-04 1:05 ` jing zhang
2010-04-04 18:08 ` tytso
2010-04-05 3:53 ` jing zhang
2010-04-05 4:27 ` Eric Sandeen
2010-04-05 4:51 ` jing zhang
2010-04-05 4:59 ` Eric Sandeen
2010-04-05 5:08 ` jing zhang [this message]
2010-04-05 12:42 ` tytso
2010-04-06 13:43 ` jing zhang
2010-04-06 14:21 ` tytso
2010-04-07 16:34 ` jing zhang
2010-04-05 5:18 ` jing zhang
2010-04-05 12:43 ` tytso
2010-03-26 8:54 ` Aneesh Kumar K. V
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=o2tac8f92701004042208l99c70297mf9955beacacd96bf@mail.gmail.com \
--to=zj.barak@gmail.com \
--cc=adilger@sun.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=shaggy@linux.vnet.ibm.com \
--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).