On Thu, 26 Jul 2007 11:46:23 +0200
Andi Kleen <[email protected]> wrote:
>
> > Look: if there's a way in which an unprivileged user can trigger a printk
> > we fix it, end of story.
>
> I'm firmly against disabling it on x86-64 by default. The printks are extremly
> useful and have found many bugs in the past.
Then add the rate limiting by default.
Lots of things are convenient. Being able to read arbitary kernel memory
from user space is frequently convenient for debugging but that doesn't
mean its a good idea or should be allowed
-
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/
[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]
