From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Should struct inode be made available to userspace?
Date: Sat, 03 Jan 2004 13:39:41 -0500 [thread overview]
Message-ID: <bt71ip$cer$1@gatekeeper.tmr.com> (raw)
In-Reply-To: <20031229195742.GL4176@parcelfarce.linux.theplanet.co.uk>
viro@parcelfarce.linux.theplanet.co.uk wrote:
> struct inode and structures containing it should not be used outside of kernel.
> Moreover, foo_fs.h should be seriously trimmed down and everything _not_
> useful outside of kernel should be taken into fs/foo/*; other kernel code
> also doesn't give a fsck for that stuff, so it should be private to filesystem
> instead of polluting include/linux/*.
Moving the definitions is fine, but some user programs, like backup
programs, do benefit from direct interpretation of the inode. Clearly
that's not a normal user program, but this information is not only
useful inside the kernel.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2004-01-03 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 19:40 Should struct inode be made available to userspace? Mariusz Mazur
2003-12-29 19:57 ` viro
2004-01-03 18:39 ` Bill Davidsen [this message]
2004-01-03 18:57 ` viro
2004-01-04 5:43 ` Bill Davidsen
2004-01-04 5:45 ` Jeff Woods
2004-01-04 6:28 ` viro
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='bt71ip$cer$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--cc=linux-kernel@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.