Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756409AbZGNUkR (ORCPT ); Tue, 14 Jul 2009 16:40:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756416AbZGNUkQ (ORCPT ); Tue, 14 Jul 2009 16:40:16 -0400 Received: from cantor.suse.de ([195.135.220.2]:34160 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756415AbZGNUkP (ORCPT ); Tue, 14 Jul 2009 16:40:15 -0400 Date: Tue, 14 Jul 2009 13:35:22 -0700 From: Greg KH To: "David P. Quigley" Cc: jmorris@namei.org, sds@tycho.nsa.gov, linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org Subject: Re: [PATCH] Security/sysfs: Enable security xattrs to be set on sysfs files, directories, and symlinks. Message-ID: <20090714203522.GA18330@suse.de> References: <20090709151803.GB24302@suse.de> <1247159613.4398.215.camel@localhost> <20090709175250.GB26378@suse.de> <1247167738.4398.229.camel@localhost> <20090709201257.GB27124@suse.de> <1247170786.4398.242.camel@localhost> <20090709204128.GA27638@suse.de> <1247589459.4398.372.camel@localhost> <20090714175007.GA9428@suse.de> <1247602566.4398.376.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1247602566.4398.376.camel@localhost> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1594 Lines: 36 On Tue, Jul 14, 2009 at 04:16:06PM -0400, David P. Quigley wrote: > On Tue, 2009-07-14 at 10:50 -0700, Greg KH wrote: > > On Tue, Jul 14, 2009 at 12:37:39PM -0400, David P. Quigley wrote: > > > So, I've been looking through the sysfs code and I can't find a > > > reference to netlink in there. I am assuming that it is other parts of > > > the kernel which make use of netlink which are calling the sysfs_* > > > functions. Any suggestions for where to look on how this is being used > > > and what the important users are? > > > > The netlink messages are coming from the kobject uevent code, look in > > lib/kobject_uevent.c for the code that creates and sends them out. This > > happens for every sysfs directory that is created that corresponds with > > a kobject. > > > > thanks, > > > > greg k-h > > It is unclear to me what if anything we need to do to the kobject_uevent > code for these changes. Do you have a particular use case in mind? Is > there some sort of notification that should be sent up to user space > when the label is changed on a file? No, the point is that userspace is notified when a kobject is created and added to sysfs. You can use that notification to then put the "correct" label on the sysfs directory and files, if they differ from your "default" value you wanted them to have. Hope this helps, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/