From: Andi Kleen <andi@firstfloor.org>
To: torvalds@linux-foundation.org, akpm@osdl.org,
ebiederm@xmission.com, linux-kernel@vger.kernel.org
Subject: [PATCH] [0/2] SYSCTL: Warn once for all legacy syctls
Date: Sat, 19 Dec 2009 15:58:31 +0100 (CET) [thread overview]
Message-ID: <20091219358.549678091@firstfloor.org> (raw)
Even with my recent patch to not warn for CTL_KERN,KERN_VERSION there
is still the theoretical possibility that some program who uses another
binary sysctl regularly will get a flooded syslog.
This patchkit changes this to only warn once for every possible binary sysctl.
-Andi
next reply other threads:[~2009-12-19 14:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 14:58 Andi Kleen [this message]
2009-12-19 14:58 ` [PATCH] [1/2] SYSCTL: Make bin_table not const Andi Kleen
2009-12-19 17:40 ` Linus Torvalds
2009-12-19 21:18 ` Andi Kleen
2009-12-20 20:06 ` Eric W. Biederman
2009-12-20 21:06 ` Andi Kleen
2009-12-21 1:23 ` [PATCH] SYSCTL: Print binary sysctl warnings (nearly) only once Andi Kleen
2009-12-19 14:58 ` [PATCH] [2/2] SYSCTL: Warn once for every binary sysctl Andi Kleen
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=20091219358.549678091@firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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