From mboxrd@z Thu Jan  1 00:00:00 1970
From: Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] pipefs unique inode numbers
Date: Tue, 30 Jan 2007 14:55:56 -0800 (PST)
Message-ID: <Pine.LNX.4.64.0701301454400.3611@woody.linux-foundation.org>
References: <Pine.LNX.4.58.0701302314210.2203@be1.lrz>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: akpm@osdl.org, Jeff Layton <jlayton@redhat.com>, dev@sw.ru,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	torvalds@osdl.org
To: Bodo Eggert <7eggert@gmx.de>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from smtp.osdl.org ([65.172.181.24]:55555 "EHLO smtp.osdl.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751960AbXA3W4p (ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
	Tue, 30 Jan 2007 17:56:45 -0500
In-Reply-To: <Pine.LNX.4.58.0701302314210.2203@be1.lrz>
Sender: linux-fsdevel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org



On Tue, 30 Jan 2007, Bodo Eggert wrote:
>
> change pipefs to use a unique inode number equal to the memory
> address unless it would be truncated.

I *really* wouldn't want to expose kernel addresses to user space, it just 
ends up being a piece of data that they shouldn't have. If we have some 
security issue, this is just too much kernel information that a bad user 
could get at.

		Linus