All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] why does struct inodes_stat_t include "int dummy[5]"?
Date: Tue, 29 May 2007 17:26:02 +0000	[thread overview]
Message-ID: <20070529172602.GE23968@parisc-linux.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0705291154450.31066@localhost.localdomain>

On Tue, May 29, 2007 at 01:10:12PM -0400, Robert P. J. Day wrote:
> > Generally these can be considered as padding, to make sure that the
> > struct uses 7 * sizeof(int), sometimes this is due to ABI
> > requirements.
> >
> > Have you checked if this is not used at all? Or if instances of this
> > struct aren't casted to something else that uses this area for some
> > purpose?
> 
> i just removed it and did "make allyesconfig" and no problem with a
> build.  so i'll submit a patch to get rid of it and see if anyone
> complains.

That's totally insufficient.  If it's part of an ABI, you won't notice
bugs caused until some random application happens to depend on it.  If
that area's being used as scratch space for something else, you'll get
buffer overruns, and subtle corruptions.

You need to go and look at *all* uses of inodes_stat, and figure out
whether removing it is safe.  Don't just post a patch; you've then put
the onus of proving you're right on someone else.
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2007-05-29 17:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 15:55 [KJ] why does struct inodes_stat_t include "int dummy[5]"? Robert P. J. Day
2007-05-29 16:20 ` Arnaldo Carvalho de Melo
2007-05-29 17:10 ` Robert P. J. Day
2007-05-29 17:26 ` Matthew Wilcox [this message]
2007-05-29 17:35 ` Arnaldo Carvalho de Melo
2007-05-29 17:44 ` Robert P. J. Day
2007-05-29 17:54 ` Matthew Wilcox
2007-05-29 19:06 ` Florian Westphal

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=20070529172602.GE23968@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=kernel-janitors@vger.kernel.org \
    /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.