From: Eric Sandeen <sandeen@sandeen.net>
To: sho@tnes.nec.co.jp
Cc: esandeen@redhat.com, ext2-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [Ext2-devel] [PATCH] fix ext3 mounts at 16T
Date: Fri, 18 Aug 2006 09:53:57 -0500 [thread overview]
Message-ID: <44E5D485.5090601@sandeen.net> (raw)
In-Reply-To: <20060818181516sho@rifu.tnes.nec.co.jp>
sho@tnes.nec.co.jp wrote:
> Hi,
>
> I had done the same work for both ext3 and ext2,
> and sent the patches to ext2-devel three months ago.
> If you need, you can get them from the following URL.
Thank you, I did not know that anyone else had done this work (I guess I should
have searched...!)
Thanks for the pointer, I will compare my patches to yours. I guess it can be
considered an independent review. :)
> I have reviewed your patch and found other place which might
> cause overflow as below. If group_first_block is the first block of
> the last group, overflow will occur. This has already been fixed
> in my patch.
I had that patch locally as well, but had not yet sent it out.
Thanks,
-Eric
next prev parent reply other threads:[~2006-08-18 14:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 9:15 [Ext2-devel] [PATCH] fix ext3 mounts at 16T sho
2006-08-18 14:53 ` Eric Sandeen [this message]
2006-08-18 17:33 ` Mingming Cao
2006-08-18 17:39 ` Eric Sandeen
2006-08-18 18:53 ` Mingming Cao
2006-08-18 23:18 ` Andreas Dilger
2006-08-18 23:56 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2006-08-11 22:13 Eric Sandeen
2006-08-11 22:29 ` [Ext2-devel] " Mingming Cao
2006-08-18 8:50 ` Andreas Dilger
2006-08-14 22:58 ` Andrew Morton
2006-08-14 23:02 ` [Ext2-devel] " Eric Sandeen
2006-08-16 11:45 ` Johann Lombardi
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=44E5D485.5090601@sandeen.net \
--to=sandeen@sandeen.net \
--cc=esandeen@redhat.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@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 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.