From: Quentin Godfroy <godfroy@clipper.ens.fr>
To: Theodore Tso <tytso@mit.edu>, Eric Sandeen <sandeen@redhat.com>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: possible (ext4 related?) memory leak in kernel 2.6.26
Date: Wed, 8 Oct 2008 02:02:27 +0200 [thread overview]
Message-ID: <20081008000227.GA32052@goelette.ens.fr> (raw)
In-Reply-To: <20081007221256.GF15929@mit.edu>
On Tue, Oct 07, 2008 at 06:12:56PM -0400, Theodore Tso wrote:
> On Mon, Oct 06, 2008 at 01:55:02PM -0400, Theodore Tso wrote:
> > Here are updates to the two patches I sent you. The first fixes some
> > printk labels and requires that the debugging dump ioctl be triggered
> > by root; the second fixes the think-o that Eric pointed out earlier
> > this morning.
>
> Hey Quentin, just wanted to check in and find out if the patches seem
> to be working for you. They seem to solve the problem on my side; I
> can no longer reproduce the problem. Is it working for you?
I rebooted, but as I didn't know exactly how to trigger the bug except than
by waiting a few days I was waiting to see.
Do you have an idea about how to trigger the bug?
Regards,
Quentin Godfroy
next prev parent reply other threads:[~2008-10-08 0:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 20:27 possible (ext4 related?) memory leak in kernel 2.6.26 Quentin Godfroy
2008-09-30 21:18 ` Theodore Tso
2008-09-30 22:23 ` Quentin
2008-10-03 0:35 ` Theodore Tso
2008-10-05 9:15 ` Quentin Godfroy
2008-10-05 12:27 ` Theodore Tso
2008-10-05 16:12 ` Quentin Godfroy
2008-10-06 2:50 ` Theodore Tso
2008-10-06 15:30 ` Eric Sandeen
2008-10-06 15:50 ` Renato S. Yamane
2008-10-06 17:55 ` Theodore Tso
2008-10-07 22:12 ` Theodore Tso
2008-10-08 0:02 ` Quentin Godfroy [this message]
2008-10-08 0:53 ` Theodore Tso
2008-10-08 23:52 ` Quentin Godfroy
2008-10-09 2:38 ` Theodore Tso
2008-10-02 18:36 ` 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=20081008000227.GA32052@goelette.ens.fr \
--to=godfroy@clipper.ens.fr \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.