Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267542AbUIOVkA (ORCPT ); Wed, 15 Sep 2004 17:40:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267438AbUIOViM (ORCPT ); Wed, 15 Sep 2004 17:38:12 -0400 Received: from [66.35.79.110] ([66.35.79.110]:35269 "EHLO www.hockin.org") by vger.kernel.org with ESMTP id S267542AbUIOVea (ORCPT ); Wed, 15 Sep 2004 17:34:30 -0400 Date: Wed, 15 Sep 2004 14:34:19 -0700 From: Tim Hockin To: Robert Love Cc: Greg KH , Kay Sievers , akpm@osdl.org, linux-kernel@vger.kernel.org Subject: Re: [patch] kernel sysfs events layer Message-ID: <20040915213419.GA21899@hockin.org> References: <1095279043.23385.102.camel@betsy.boston.ximian.com> <20040915202234.GA18242@hockin.org> <1095279985.23385.104.camel@betsy.boston.ximian.com> <20040915203133.GA18812@hockin.org> <1095280414.23385.108.camel@betsy.boston.ximian.com> <20040915204754.GA19625@hockin.org> <1095281358.23385.109.camel@betsy.boston.ximian.com> <20040915205643.GA19875@hockin.org> <20040915212322.GB25840@kroah.com> <1095283589.23385.117.camel@betsy.boston.ximian.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1095283589.23385.117.camel@betsy.boston.ximian.com> User-Agent: Mutt/1.4.2i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1151 Lines: 26 On Wed, Sep 15, 2004 at 05:26:29PM -0400, Robert Love wrote: > On Wed, 2004-09-15 at 14:23 -0700, Greg KH wrote: > > > We aren't giving absolute /dev entries here, that's the beauty of the > > kobject tree :) > > Not that I agree, but I don't think it is the absolute /dev entries that > bother him: it is the fact that knowledge of the mount itself is an > information leak. > > Which it is. As root, in my name space, I should rest in the knowledge > that my mounts are secret, I guess. But I just do not see it as a big > problem. It's a can of worms, is what it is. And I'm not sure what a good fix would be. Would it just be enough to send a generic "mount-table changed" event, and let userspace figure out the rest? Or really, why is the kernel broadcasting a mount, which originated in userland. Couldn't mount (or a mount wrapper) do that? It's already running in the right namespace... - 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/