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:33:14 -0700 [thread overview]
Message-ID: <465C71EA.5040706@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0705291416470.4736@localhost.localdomain>
Robert P. J. Day wrote:
> On Tue, 29 May 2007, Randy Dunlap wrote:
>
>> On Tue, 29 May 2007 14:07:01 -0400 (EDT) Robert P. J. Day wrote:
>>
>>> On Tue, 29 May 2007, Andrew Morton wrote:
>>>
>>>> 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.
>
> so, just to clarify, what *is* the value of those trailing five
> zeroes? andrew suggests it's to be backward-compatible with an old
> kernel, which doesn't make much sense to me. it would make more sense
> to say that that's backward-compatible with some old userspace app
> that always wants to see seven values and just ignores the last five.
Agreed, it's for compat with some (unknown) userspace app that reads
/proc/sys/fs/inode-state and scans for 7 (or more than 2) numbers there.
The mantra is "don't break userspace," so we leave the numbers there...
> in any event, from Documentation/filesystems/proc.txt:
>
> "inode-state contains two actual numbers and five dummy values. The
> numbers are nr_inodes and nr_free_inodes (in order of appearance)."
>
> if even the documentation calls them dummy values, do they really have
> any residual value at this point? and on that note, i'll stop harping
> on this and move on.
>
> rday
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-05-29 18:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 17:11 [PATCH] FILESYSTEMS: Delete unused "int dummy[5]" from inodes_stat_t 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
2007-05-29 18:21 ` Robert P. J. Day
2007-05-29 18:33 ` Randy Dunlap [this message]
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=465C71EA.5040706@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