From: Eric Sandeen <sandeen@redhat.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Chuck Ebbert <cebbert@redhat.com>,
Kirill Korotaev <dev@openvz.org>,
sct@redhat.com, akpm@linux-foundation.org, adilger@clusterfs.com,
linux-ext4@vger.kernel.org
Subject: Re: [RFC: 2.6.16 patch] ext3: fix ext3 block bitmap leakage
Date: Tue, 20 Feb 2007 11:08:37 -0600 [thread overview]
Message-ID: <45DB2B15.70603@redhat.com> (raw)
In-Reply-To: <20070220151950.GV13958@stusta.de>
Adrian Bunk wrote:
> On Mon, Feb 19, 2007 at 06:03:14PM -0500, Chuck Ebbert wrote:
>
>> This was dropped from 2.6.16-stable somehow:
>>
>> http://lkml.org/lkml/2006/6/30/54
>
> Thanks for forwarding it.
>
> This patch didn't went in this form into Linus' tree, I'd therefore like
> to get an ACK from the ext3 maintainers (Cc'ed) before applying it.
Yep, ACK from me for 2.6.16-stable.
-Eric
next prev parent reply other threads:[~2007-02-20 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45DA2CB2.4080507@redhat.com>
2007-02-20 15:19 ` [RFC: 2.6.16 patch] ext3: fix ext3 block bitmap leakage Adrian Bunk
2007-02-20 17:08 ` Eric Sandeen [this message]
2007-02-26 14:35 ` Adrian Bunk
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=45DB2B15.70603@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@clusterfs.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@stusta.de \
--cc=cebbert@redhat.com \
--cc=dev@openvz.org \
--cc=linux-ext4@vger.kernel.org \
--cc=sct@redhat.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