public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Juhl <juhl@eisenstein.dk>
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 15:39:06 +0200	[thread overview]
Message-ID: <3BCD89FA.6050209@eisenstein.dk> (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?

I would like to give it a try. Seems like a good little project for one 
who is trying to learn his way around the kernel :)  It will probably 
take me a lot longer than one of the experienced kernel hackers and 
would probably not be perfect on the first try, but I'm willing to 
invest some time in it.


Best regards,
Jesper Juhl




  reply	other threads:[~2001-10-17 13:46 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 [this message]
2001-10-17 13:53   ` Keith Owens
2001-10-17 15:00 ` Geert Uytterhoeven
2001-10-17 15:29 ` Randy.Dunlap

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=3BCD89FA.6050209@eisenstein.dk \
    --to=juhl@eisenstein.dk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox