From: Christoph Lameter <clameter@sgi.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Mingming Cao <cmm@us.ibm.com>, Takashi Sato <sho@tnes.nec.co.jp>,
linux-fsdevel@vger.kernel.org, jack@suse.cz
Subject: Re: [patch 2/4] ext2: fix rec_len overflow for 64KB block size
Date: Wed, 26 Sep 2007 10:27:47 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0709261026100.15435@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070926004245.GS32520@schatzie.adilger.int>
On Tue, 25 Sep 2007, Andreas Dilger wrote:
> On Sep 25, 2007 16:30 -0700, Christoph Lameter wrote:
> > [2/4] ext2: fix rec_len overflow
> > - prevent rec_len from overflow with 64KB blocksize
> >
> > Signed-off-by: Takashi Sato <sho@tnes.nec.co.jp>
> > Signed-off-by: Mingming Cao <cmm@us.ibm.com>
> > Signed-off-by: Christoph Lameter <clameter@sgi.com>
>
> Note that we just got a cleaner implemantation of this code on the ext4
> mailing list from Jan Kara yesterday. Please use that one instead, in
> thread "Avoid rec_len overflow with 64KB block size" instead.
Yes that looks much better. He is missing the first patch that changes the
constants.
How can we get the 4 patches (the constant change and Jan's changes to ext
2 3 4 merged?
next prev parent reply other threads:[~2007-09-26 17:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 23:30 [patch 0/4] 64k pagesize/blocksize fixes Christoph Lameter
2007-09-25 23:30 ` [patch 1/4] Increase limits for 64k page size support for Ext2/3/4 Christoph Lameter
2007-09-25 23:30 ` [patch 2/4] ext2: fix rec_len overflow for 64KB block size Christoph Lameter
2007-09-26 0:42 ` Andreas Dilger
2007-09-26 17:27 ` Christoph Lameter [this message]
2007-09-25 23:30 ` [patch 3/4] ext3: fix rec_len overflow with " Christoph Lameter
2007-09-25 23:30 ` [patch 4/4] ext4: fix rec_len overflow for " Christoph Lameter
2007-09-26 17:58 ` [patch 0/4] 64k pagesize/blocksize fixes Mingming Cao
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=Pine.LNX.4.64.0709261026100.15435@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=adilger@clusterfs.com \
--cc=cmm@us.ibm.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sho@tnes.nec.co.jp \
/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).