From: Christoph Hellwig <hch@infradead.org>
To: Theodore Tso <tytso@mit.edu>,
Christoph Hellwig <hch@infradead.org>,
Peter Staubach <staubach@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH]: ext4: fix big endian
Date: Thu, 6 Nov 2008 12:39:44 -0500 [thread overview]
Message-ID: <20081106173944.GA23398@infradead.org> (raw)
In-Reply-To: <20081106173327.GF18939@mit.edu>
On Thu, Nov 06, 2008 at 12:33:27PM -0500, Theodore Tso wrote:
> On Thu, Nov 06, 2008 at 11:38:46AM -0500, Christoph Hellwig wrote:
> >
> > Yes. And if someone ran sparse over the code both the initial error
> > and this varaint would be trivial to spot..
> >
>
> That's how Aneesh found it. :-)
Heh, okay. We really should try to find some annotations that run
sparse with endian checking by default for those parts of the tree
where it makes sense..
next prev parent reply other threads:[~2008-11-06 17:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 15:00 EXT4-fs: not enough memory for 522250 flex groups Christian Borntraeger
2008-11-06 15:51 ` [PATCH]: ext4: fix big endian (was: not enough memory for 522250 flex groups) Christian Borntraeger
2008-11-06 16:06 ` [PATCH]: ext4: fix big endian Peter Staubach
2008-11-06 16:15 ` Christian Borntraeger
2008-11-06 16:32 ` Aneesh Kumar K.V
2008-11-06 16:38 ` Christoph Hellwig
2008-11-06 17:11 ` Christian Borntraeger
2008-11-06 17:33 ` Theodore Tso
2008-11-06 17:39 ` Christoph Hellwig [this message]
2008-11-06 17:48 ` Alexey Dobriyan
2008-11-08 22:35 ` Jörn Engel
2008-11-10 18:09 ` Harvey Harrison
2008-11-10 19:31 ` Jörn Engel
2008-11-06 16:06 ` [PATCH]: ext4: fix big endian (was: not enough memory for 522250 flex groups) Andreas Schwab
2008-11-06 16:59 ` Theodore Tso
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=20081106173944.GA23398@infradead.org \
--to=hch@infradead.org \
--cc=borntraeger@de.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=staubach@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox