From: Andrew Morton <akpm@linux-foundation.org>
To: Rene Herman <rene.herman@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Andi Kleen <ak@suse.de>,
Masoud Sharbiani <masouds@google.com>,
Kirill Korotaev <dev@openvz.org>,
linux-kernel@vger.kernel.org
Subject: Re: i386-show-unhandled-signals-v3
Date: Thu, 26 Jul 2007 03:25:16 -0700 [thread overview]
Message-ID: <20070726032516.3de343c6.akpm@linux-foundation.org> (raw)
In-Reply-To: <46A874B8.7000407@gmail.com>
On Thu, 26 Jul 2007 12:17:28 +0200 Rene Herman <rene.herman@gmail.com> wrote:
> On 07/26/2007 12:16 PM, Alan Cox wrote:
>
> > On Thu, 26 Jul 2007 11:46:23 +0200
> > Andi Kleen <ak@suse.de> 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.
>
> The messages were rate limited -- Andrew said they couldn't be on default even
> rate limited.
>
Andrew didn't think too hard, sorry. I agree that on-by-default is a reasonable
compromise once they're rate-limited.
prev parent reply other threads:[~2007-07-26 10:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 15:47 i386-show-unhandled-signals-v3 Masoud Asgharifard Sharbiani
2007-07-25 14:45 ` i386-show-unhandled-signals-v3 Kirill Korotaev
2007-07-25 14:50 ` i386-show-unhandled-signals-v3 Masoud Sharbiani
2007-07-25 15:01 ` i386-show-unhandled-signals-v3 Kirill Korotaev
2007-07-25 14:57 ` i386-show-unhandled-signals-v3 Andi Kleen
2007-07-25 21:04 ` i386-show-unhandled-signals-v3 Andrew Morton
2007-07-25 21:07 ` i386-show-unhandled-signals-v3 Masoud Sharbiani
2007-07-25 23:25 ` i386-show-unhandled-signals-v3 Andrew Morton
2007-07-25 23:40 ` i386-show-unhandled-signals-v3 Masoud Asgharifard Sharbiani
2007-07-25 23:58 ` i386-show-unhandled-signals-v3 Andrew Morton
2007-07-26 3:21 ` i386-show-unhandled-signals-v3 Masoud Sharbiani
2007-07-26 4:15 ` i386-show-unhandled-signals-v3 Andrew Morton
2007-07-26 9:13 ` i386-show-unhandled-signals-v3 Rene Herman
2007-07-26 9:46 ` i386-show-unhandled-signals-v3 Andi Kleen
2007-07-26 10:14 ` i386-show-unhandled-signals-v3 Andrew Morton
2007-07-26 11:59 ` i386-show-unhandled-signals-v3 Andi Kleen
2007-07-26 12:18 ` i386-show-unhandled-signals-v3 Alan Cox
2007-07-26 10:16 ` i386-show-unhandled-signals-v3 Alan Cox
2007-07-26 10:17 ` i386-show-unhandled-signals-v3 Rene Herman
2007-07-26 10:25 ` Andrew Morton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070726032516.3de343c6.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dev@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masouds@google.com \
--cc=rene.herman@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox