The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Philippe Elie <phil.el@wanadoo.fr>
To: Zwane Mwaikambo <zwane@holomorphy.com>
Cc: Russell King <rmk@arm.linux.org.uk>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.45 odd deref in serial_in
Date: Wed, 06 Nov 2002 03:23:13 +0000	[thread overview]
Message-ID: <3DC88B21.3030202@wanadoo.fr> (raw)
In-Reply-To: Pine.LNX.4.44.0211050927350.27141-100000@montezuma.mastecende.com

Zwane Mwaikambo wrote:
> On Tue, 5 Nov 2002, Russell King wrote:
> 
> 
>>static _INLINE_ unsigned int serial_in(struct uart_8250_port *up, int offset)
>>{
>>        offset <<= up->port.regshift;
>>
>>        switch (up->port.iotype) {
>>
>>which also dereferences "up".  So something may have corrupted %ebx
>>between executing that switch statement and executing the inb().
>>
>>Could the NMI handler be corrupting %ebx ?

ok but

 > [<c023d9d8>] serial8250_console_write+0x68/0x1f0
 > [<c0121459>] __call_console_drivers+0x49/0x50
 > [<c0121541>] call_console_drivers+0x71/0x100
 > [<c012196d>] release_console_sem+0xbd/0x170
 > [<c01217cc>] printk+0x18c/0x220
 > [<c01170d5>] nmi_add_task+0xc5/0xe0
 > [<c01177e0>] nmi_watchdog_tick+0x0/0x120

the oops occur during a NMI so I wonder how a NMI
can occur and clobber ebx

-- 
Philippe Elie


  reply	other threads:[~2002-11-06  2:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-05  4:27 2.5.45 odd deref in serial_in Zwane Mwaikambo
2002-11-05  4:38 ` Zwane Mwaikambo
2002-11-05  9:02 ` Russell King
2002-11-05  9:20   ` Zwane Mwaikambo
2002-11-05 10:16     ` Russell King
2002-11-07 15:17     ` David Woodhouse
2002-11-07 15:24       ` Zwane Mwaikambo
2002-11-05 10:20 ` Russell King
2002-11-05 14:30   ` Zwane Mwaikambo
2002-11-06  3:23     ` Philippe Elie [this message]
2002-11-06  8:37       ` Zwane Mwaikambo

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=3DC88B21.3030202@wanadoo.fr \
    --to=phil.el@wanadoo.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=zwane@holomorphy.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