From owner-freebsd-current@FreeBSD.ORG Wed Jan 22 22:36:04 2014 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 82389FFB for ; Wed, 22 Jan 2014 22:36:04 +0000 (UTC) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 461A51AFC for ; Wed, 22 Jan 2014 22:36:03 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id A84567300A; Wed, 22 Jan 2014 23:38:36 +0100 (CET) Date: Wed, 22 Jan 2014 23:38:36 +0100 From: Luigi Rizzo To: current@freebsd.org Subject: any use for sys/sys/selinfo.h outside the kernel ? Message-ID: <20140122223836.GA292@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jan 2014 22:36:04 -0000 Looking at sys/sys/selinfo.h i see that parts of it are in #ifdef _KERNEL ... #endif but it seems to me that also the remaining content (definition of struct selinfo) is only of use within the kernel -- or possibly to programs who want to peek into kmem. So i wonder, does it make sense to have the #ifdef _KERNEL guard at all, or should we push it to the entire content of the file ? Same goes probably for other files in sys/sys describing kernel data structures, e.g. sys/sys/socketvar.h etc. cheers luigi