From: Eric Sandeen <sandeen@redhat.com>
To: nicholas.dokos@hp.com
Cc: Theodore Ts'o <tytso@mit.edu>,
linux-ext4@vger.kernel.org, Andreas Dilger <adilger@sun.com>,
Justin Maggard <jmaggard10@gmail.com>,
Ric Wheeler <rwheeler@redhat.com>
Subject: Re: [PATCH] Fix ext2fs_set_gdt_csum() to use access functions.
Date: Thu, 03 Sep 2009 00:12:48 -0500 [thread overview]
Message-ID: <4A9F5050.1010702@redhat.com> (raw)
In-Reply-To: <15737.1251954670@gamaville.dokosmarshall.org>
Nick Dokos wrote:
> Eric Sandeen <sandeen@redhat.com> wrote:
>
>>> Replace all field accesses with calls to access functions.
>>> Most importantly, get rid of the mis-declared group descriptor
>>> pointer which caused the wrong fields to be updated.
>> Not quite sure what you mean by this? It worked ok for the "old" size ...
>>
>
> Yes, it worked fine for the old ext2_group_desc structure, but it has no
> hope of working with the ext4_group_desc: the sizes are different, so
> doing bg++ gets it pointing somewhere within the first descriptor, not
> to the beginning of the second. That's how it ended up modifying
> reserved fields.
right. Ok, I was just confused when you said "mis-declared" - thought
you meant something was wrong with how bg was set or initialized.
> Sorry about the whitespace problems. As for the flags, I didn't worry
> too much about how to set them: I figured that once the dust settles,
> we'll follow the proper convention.
sounds good.
Thanks,
-Eric
> Thanks for looking it over and testing too! We'll see whether Justin's
> problem disappears.
>
> Nick
next prev parent reply other threads:[~2009-09-03 5:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 3:21 [PATCH] Fix ext2fs_set_gdt_csum() to use access functions Nick Dokos
2009-09-03 4:51 ` Eric Sandeen
2009-09-03 5:11 ` Nick Dokos
2009-09-03 5:12 ` Eric Sandeen [this message]
2009-09-03 18:16 ` Justin Maggard
2009-09-03 5:21 ` Andreas Dilger
-- strict thread matches above, loose matches on Subject: below --
2009-09-03 5:22 Nick Dokos
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=4A9F5050.1010702@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@sun.com \
--cc=jmaggard10@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=nicholas.dokos@hp.com \
--cc=rwheeler@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.