From: Nikita Danilov <Nikita@Namesys.COM>
To: Alexander Viro <viro@math.psu.edu>
Cc: Andrew Morton <akpm@zip.com.au>,
lkml <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [patch] ext2_fill_super breakage
Date: Thu, 28 Mar 2002 17:36:46 +0300 [thread overview]
Message-ID: <15523.10878.394037.864862@laputa.namesys.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0203280918190.24447-100000@weyl.math.psu.edu>
Alexander Viro writes:
>
>
> On Wed, 27 Mar 2002, Andrew Morton wrote:
>
> > In 2.5.7 there is a thinko in the allocation and initialisation
> > of the fs-private superblock for ext2. It's passing the wrong type
> > to the sizeof operator (which of course gives the wrong size)
> > when allocating and clearing the memory.
>
> > Lesson for the day: this is one of the reasons why this idiom:
> >
> > some_type *p;
> >
> > p = malloc(sizeof(*p));
> > ...
> > memset(p, 0, sizeof(*p));
> >
> > is preferable to
> >
> > some_type *p;
> >
> > p = malloc(sizeof(some_type));
> > ...
> > memset(p, 0, sizeof(some_type));
>
> ... however, there is a lot of reasons why the former is preferable.
> For one thing, the latter is hell on any search. Moreover, I would
> argue that memset() on a structure is not a good idea - better do
> the explicit initialization.
Explicit initialization always leaves room for some "pad" field inserted
by compiler for alignment to be left with garbage. This is more than
just annoyance when structure is something that will be written to the
disk. Reiserfs had such problems.
>
>
Nikita.
next prev parent reply other threads:[~2002-03-28 14:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-28 7:30 Andrew Morton
2002-03-28 13:34 ` Brian Gerst
2002-03-28 13:46 ` Rob Landley
2002-03-28 13:50 ` Jos Hulzink
2002-03-28 17:26 ` Bill Davidsen
2002-03-28 17:27 ` Andrew Morton
2002-03-28 18:13 ` Brian Gerst
2002-03-28 14:21 ` Alexander Viro
2002-03-28 14:36 ` Nikita Danilov [this message]
2002-03-28 14:48 ` Alexander Viro
2002-03-28 14:51 ` Nikita Danilov
2002-03-28 15:20 ` Alexander Viro
2002-03-28 14:50 ` Arjan van de Ven
2002-03-28 15:01 ` Nikita Danilov
2002-03-28 17:45 ` Andrew Morton
2002-03-28 23:51 ` Alexander Viro
2002-03-29 0:25 ` Andrew Morton
2002-03-29 5:14 ` Andreas Dilger
2002-03-29 8:06 ` Guest section DW
2002-03-29 15:45 ` Bill Davidsen
2002-03-29 0:42 ` Bill Davidsen
2002-03-28 22:45 ` Brian Gerst
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=15523.10878.394037.864862@laputa.namesys.com \
--to=nikita@namesys.com \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.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
all inboxes | Powered by JetHome®