From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org, linux-ia64@linuxia64.org
Subject: Re: console_loglevel is broken on ia64
Date: Wed, 17 Oct 2001 08:29:43 -0700 [thread overview]
Message-ID: <3BCDA3E7.7D201103@osdl.org> (raw)
In-Reply-To: <2784.1003325102@ocs3.intra.ocs.com.au>
Keith Owens wrote:
>
> kernel/printk.c has this abomination.
>
> /* Keep together for sysctl support */
> int console_loglevel = DEFAULT_CONSOLE_LOGLEVEL;
> int default_message_loglevel = DEFAULT_MESSAGE_LOGLEVEL;
> int minimum_console_loglevel = MINIMUM_CONSOLE_LOGLEVEL;
> int default_console_loglevel = DEFAULT_CONSOLE_LOGLEVEL;
>
> sysctl assumes that the 4 variables occupy contiguous storage. They
> don't on ia64, console_loglevel is separate from the other variables.
>
> echo 6 4 1 7 > /proc/sys/kernel/printk
>
> on ia64 overwrites console_loglevel and the next 3 integers, whatever
> they happen to be. On 2.4.12 it corrupts console_sem, other ia64
> kernels will corrupt different data.
>
> Does anybody fancy a small project to clean up these variables? They
> need to become an integer array (say console_printk) containing 4
> elements, which is what sysctl assumes. All references to these fields
> have to be changed to refer to the corresponding array element. That
> should be as simple as
Yep. I asked someone to clean this up about
3 weeks ago, and he said that he would do so, but....?
So Jesper or someone else should jump on it.
~Randy
prev parent reply other threads:[~2001-10-17 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-17 13:25 console_loglevel is broken on ia64 Keith Owens
2001-10-17 13:39 ` Jesper Juhl
2001-10-17 13:53 ` Keith Owens
2001-10-17 15:00 ` Geert Uytterhoeven
2001-10-17 15:29 ` Randy.Dunlap [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=3BCDA3E7.7D201103@osdl.org \
--to=rddunlap@osdl.org \
--cc=kaos@ocs.com.au \
--cc=linux-ia64@linuxia64.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.