mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] FILESYSTEMS:  Delete unused "int dummy[5]" from inodes_stat_t.
Date: Tue, 29 May 2007 11:19:02 -0700	[thread overview]
Message-ID: <20070529111902.27055fd0.randy.dunlap@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0705291406040.4617@localhost.localdomain>

On Tue, 29 May 2007 14:07:01 -0400 (EDT) Robert P. J. Day wrote:

> On Tue, 29 May 2007, Andrew Morton wrote:
> 
> > On Tue, 29 May 2007 13:11:07 -0400 (EDT)
> > "Robert P. J. Day" <rpjday@mindspring.com> wrote:
> >
> > >
> > > Delete the apparently unused array "int dummy[5]" from struct
> > > inodes_stat_t.
> > >
> > > Signed-off-by: Robert P. J. Day <rpjday@mindspring.com>
> > >
> > > ---
> > >
> > >   no idea what that array is for, but no one seems to care about it.
> > > removal compile-tested on x86 with "make allyesconfig" and nobody
> > > misses it (unless it's used for padding of some kind).
> > >
> > >
> > > diff --git a/include/linux/fs.h b/include/linux/fs.h
> > > index 7cf0c54..dec83dd 100644
> > > --- a/include/linux/fs.h
> > > +++ b/include/linux/fs.h
> > > @@ -44,7 +44,6 @@ extern int get_max_files(void);
> > >  struct inodes_stat_t {
> > >  	int nr_inodes;
> > >  	int nr_unused;
> > > -	int dummy[5];
> > >  };
> > >  extern struct inodes_stat_t inodes_stat;
> > >
> >
> > kernel/sysctl.c:
> >
> > 	{
> > 		.ctl_name	= FS_STATINODE,
> > 		.procname	= "inode-state",
> > 		.data		= &inodes_stat,
> > 		.maxlen		= 7*sizeof(int),
> > 		.mode		= 0444,
> > 		.proc_handler	= &proc_dointvec,
> > 	},
> >
> > akpm:/home/akpm> cat /proc/sys/fs/inode-state
> > 608039  178454  0       0       0       0       0
> >
> > So it _is_ used: to present those five zeroes.  I think this is for
> > back-compatibility with some cretaceous-era kernel.
> 
> ah, gotcha.  well, i'll leave this up to someone else to do anything
> with if they are so inclined.

There's little to be done, except possibly put a /* comment */
on the struct's dummy line so that we don't go thru this again
in N years.


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2007-05-29 18:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 17:11 Robert P. J. Day
2007-05-29 18:00 ` Andrew Morton
2007-05-29 18:07   ` Robert P. J. Day
2007-05-29 18:19     ` Randy Dunlap [this message]
2007-05-29 18:21       ` Robert P. J. Day
2007-05-29 18:33         ` Randy Dunlap
2007-05-29 18:44           ` Josh Boyer
2007-05-29 19:33             ` Randy Dunlap
2007-05-30  6:41               ` Stefan Richter
2007-05-30 11:29                 ` Adrian Bunk
2007-05-30 11:38                   ` Robert P. J. Day
2007-05-30 19:01                     ` [trivial PATCH, updated] fs: clarify "dummy" member in struct inodes_stat_t Stefan Richter
2007-05-30 19:16                       ` Randy Dunlap
2007-05-29 18:04 ` [PATCH] FILESYSTEMS: Delete unused "int dummy[5]" from inodes_stat_t Alexey Dobriyan

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=20070529111902.27055fd0.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.com \
    --cc=viro@zeniv.linux.org.uk \
    /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

Powered by JetHome