| To: | Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com> |
|---|---|
| Subject: | Re: kernel/printk.c problem |
| From: | Jun Sun <jsun@mvista.com> |
| Date: | Wed, 18 Apr 2001 10:32:27 -0700 |
| Cc: | Scott A McConnell <samcconn@cotw.com>, linux-mips@oss.sgi.com |
| References: | <Pine.GSO.4.10.10104180852450.17832-100000@escobaria.sonytel.be> |
| Sender: | owner-linux-mips@oss.sgi.com |
Geert Uytterhoeven wrote:
>
> On Tue, 17 Apr 2001, Scott A McConnell wrote:
> > struct console *console_drivers = NULL; <----
> > Need the NULL.
> >
> > Otherwise, bad things can happen on the following statement in printk
> >
> > ~line 311
> >
> > if ((c->flags & CON_ENABLED) && c->write){
>
> Current policy is not explicitly initializing variables to zero. If this
> causes
> problems, there's a bug in the routine that clears the BSS on kernel entry.
>
Interesting. What is the reason behind the policy? Is that because
initialized variable are put in a different section that takes more size in
the image?
Jun
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Linux on LSI EZ4102, Quinn Jensen |
|---|---|
| Next by Date: | Re: Indy and the multiple disk problem, Klaus Naumann |
| Previous by Thread: | Re: kernel/printk.c problem, Scott A McConnell |
| Next by Thread: | Re: kernel/printk.c problem, Juan Quintela |
| Indexes: | [Date] [Thread] [Top] [All Lists] |