From: Eric Sandeen <sandeen@redhat.com>
To: jing zhang <zj.barak@gmail.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: Sun, 04 Apr 2010 23:59:00 -0500 [thread overview]
Message-ID: <4BB96E14.9010903@redhat.com> (raw)
In-Reply-To: <t2pac8f92701004042151x3b0c27e2h805778b7b3aeefba@mail.gmail.com>
jing zhang wrote:
> 2010/4/5, Eric Sandeen <sandeen@redhat.com>:
>> jing zhang wrote:
>>> 2010/4/5, tytso@mit.edu <tytso@mit.edu>:
>>>> On Sun, Apr 04, 2010 at 09:05:14AM +0800, jing zhang wrote:
>>>>
>>>> How much testing are you doing before submitting patches, out of
>>>> curiosity?
>>> Yes, Ted, it is curiosity that drives me to do hard works, including patch
>>> ext4.
>> It is the language barrier that is making some of this difficult,
>> but I'm not complaining - you speak English much better than I speak any
>
> You are good guy:) Is English your native language? And, I am curious,
> what is the second language you are able to speak, Eric?
Only a little German.
>> second language. :)
>>
>> Ted meant that -he- was curious about how much testing you were doing.
>
> How do know what Ted meant, by iphone?
No, because I am a native English speaker and I understood the
figure of speech. ("out of curiosity")
> I am not good at testing, partially because it is hard to setup the
> required environment, sometimes several hard disks are needed, maybe a
> few boxes, but I try to analyse the C code while reading and
> understanding the works by great maintainers and developers of Linux
> kernel.
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)
-Eric
> - zj
next prev parent reply other threads:[~2010-04-05 4:59 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 [this message]
2010-04-05 5:08 ` jing zhang
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=4BB96E14.9010903@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@sun.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=shaggy@linux.vnet.ibm.com \
--cc=tytso@mit.edu \
--cc=zj.barak@gmail.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).