From: Andrew Morton <akpm@linux-foundation.org>
To: "Masoud Sharbiani" <masouds@google.com>
Cc: "Andi Kleen" <ak@suse.de>, "Kirill Korotaev" <dev@openvz.org>,
linux-kernel@vger.kernel.org
Subject: Re: i386-show-unhandled-signals-v3
Date: Wed, 25 Jul 2007 16:25:28 -0700 [thread overview]
Message-ID: <20070725162528.7d485ff8.akpm@linux-foundation.org> (raw)
In-Reply-To: <4517d1380707251407v178068baxcc76a86f8337cc27@mail.gmail.com>
On Wed, 25 Jul 2007 14:07:56 -0700
"Masoud Sharbiani" <masouds@google.com> wrote:
> On 7/25/07, Andrew Morton <akpm@linux-foundation.org> wrote:
> > On Wed, 25 Jul 2007 16:57:43 +0200
> > Andi Kleen <ak@suse.de> wrote:
> >
> > > On Wednesday 25 July 2007 16:45, Kirill Korotaev wrote:
> > > > plz don't enable it by default... :/
> > > > any user can spam syslog with these messages and if syslog is run as root
> > > > can take the whole diskspace...
> > >
> > > There are plenty of other ways to cause syslog messages anyways;
> >
> > tell us what they are and we'll fix them?
> >
> > > this argument is 100% bogus.
> >
> > people don't like leaving themselves open to logspamming.
> >
> >
> > For this particular issue: someone please send a patch.
> >
> Andrew,
> This is rate limited; Do you need me to rewrite it with it being
> disabled by default?
>
Yes please.
Look: if there's a way in which an unprivileged user can trigger a printk
we fix it, end of story. I don't know why this even slightly
controversial.
next prev parent reply other threads:[~2007-07-25 23:26 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 ` Andrew Morton [this message]
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 ` i386-show-unhandled-signals-v3 Andrew Morton
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=20070725162528.7d485ff8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@suse.de \
--cc=dev@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masouds@google.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