Re: [PATCH] pipefs unique inode numbers

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH] pipefs unique inode numbers
    • From: Jeff Layton <[email protected]>

• References:
  • [PATCH] pipefs unique inode numbers
    • From: Bodo Eggert <[email protected]>

• Prev by Date: Re: [PATCH 0 of 4] Generic AIO by scheduling stacks
• Next by Date: Re: Hidden SSID's
• Previous by thread: [PATCH] pipefs unique inode numbers
• Next by thread: Re: [PATCH] pipefs unique inode numbers
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]