mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Lundell <jlundell@lundell-bros.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ethtool.h should use userspace-accessible types
Date: Mon, 15 Mar 2004 13:24:41 -0800	[thread overview]
Message-ID: <p0610033abc7bceda4ffd@[192.168.0.3]> (raw)
In-Reply-To: <20040314032501.GT20174@waste.org>

At 9:25 PM -0600 3/13/04, Matt Mackall wrote:
>On Fri, Mar 12, 2004 at 01:48:54PM -0800, Jonathan Lundell wrote:
>>  At 10:06 AM -0700 3/12/04, Eric W. Biederman wrote:
>>  >My intent was to say:  Why change the types when there is no #ifdef
>>  >__KERNEL__ in the header.  With no #ifdef __KERNEL__ it exports
>>  >definitions that are private to the kernel making it not safe for
>>  >userspace to use.  With kernel private definitions in there it will
>>  >generate name space pollution if included by user space.
>>
>>  Presumably because it *is* included by userspace, because it defines
>>  the interface between the kernel and userspace; of course userspace
>>  will (does) include it.
>
>Well that's a bug. You don't include kernel headers in userspace.
>Doing so has been deprecated for 8 years and 3 major releases.

Then it's a bug for the ethtool maintainer. ethtool.c #includes 
ethtool-copy.h, a renamed copy of the kernel header file.

I'm familiar with the deprecation and continue to be bewildered by 
it. To take this particular example, ethtool.h defines an interface 
between a kernel facility and a userspace client. What's the 
non-deprecated method of sharing the interface definition?
-- 
/Jonathan Lundell.

  reply	other threads:[~2004-03-15 21:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-12  1:54 Eric Brower
2004-03-12  2:35 ` Tim Hockin
2004-03-12  4:57   ` Greg KH
2004-03-12  9:19     ` Tim Hockin
2004-03-12 16:25 ` Eric W. Biederman
2004-03-12 16:54   ` Jeff Garzik
2004-03-12 17:06     ` Eric W. Biederman
2004-03-12 21:48       ` Jonathan Lundell
2004-03-14  3:25         ` Matt Mackall
2004-03-15 21:24           ` Jonathan Lundell [this message]
2004-03-12 16:54 ` Jeff Garzik

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='p0610033abc7bceda4ffd@[192.168.0.3]' \
    --to=jlundell@lundell-bros.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 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®