From: Andrew Morton <akpm@osdl.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] arch/i386/kernel/io_apic.c: handle a negative return value
Date: Mon, 13 Nov 2006 16:42:56 -0800 [thread overview]
Message-ID: <20061113164256.805a7497.akpm@osdl.org> (raw)
In-Reply-To: <20061112174826.GC3382@stusta.de>
On Sun, 12 Nov 2006 18:48:26 +0100
Adrian Bunk <bunk@stusta.de> wrote:
> The Coverity checker noted that bad things might happen if
> find_isa_irq_apic() returned -1.
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
>
> --- linux-2.6/arch/i386/kernel/io_apic.c.old 2006-11-12 18:41:24.000000000 +0100
> +++ linux-2.6/arch/i386/kernel/io_apic.c 2006-11-12 18:42:00.000000000 +0100
> @@ -2160,7 +2160,8 @@ static inline void unlock_ExtINT_logic(v
>
> pin = find_isa_irq_pin(8, mp_INT);
> apic = find_isa_irq_apic(8, mp_INT);
> - if (pin == -1)
> +
> + if ((pin == -1) || (apic == -1))
> return;
>
I dunno about this. For some reason I don't trust the apic code much. At
present if find_isa_irq_apic() fails we at least have a chance of
blundering into a nnice oops or something. By adding correct
error-checking we increase the chance of things just silently not working.
So let's see what this does...
From: Adrian Bunk <bunk@stusta.de>
The Coverity checker noted that bad things might happen if
find_isa_irq_apic() returned -1.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Cc: Andi Kleen <ak@suse.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
---
arch/i386/kernel/io_apic.c | 10 +++++++++-
1 files changed, 9 insertions(+), 1 deletion(-)
diff -puN arch/i386/kernel/io_apic.c~arch-i386-kernel-io_apicc-handle-a-negative-return-value arch/i386/kernel/io_apic.c
--- a/arch/i386/kernel/io_apic.c~arch-i386-kernel-io_apicc-handle-a-negative-return-value
+++ a/arch/i386/kernel/io_apic.c
@@ -2166,9 +2166,17 @@ static inline void unlock_ExtINT_logic(v
unsigned char save_control, save_freq_select;
pin = find_isa_irq_pin(8, mp_INT);
+ if (pin == -1) {
+ printk(KERN_ERR "unlock_ExtINT_logic: find_isa_irq_pin()
+ "failed\n");
+ return;
+ }
apic = find_isa_irq_apic(8, mp_INT);
- if (pin == -1)
+ if (apic == -1) {
+ printk(KERN_ERR "unlock_ExtINT_logic: find_isa_irq_apic()
+ "failed\n");
return;
+ }
entry0 = ioapic_read_entry(apic, pin);
clear_IO_APIC_pin(apic, pin);
_
next prev parent reply other threads:[~2006-11-14 0:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-12 17:48 Adrian Bunk
2006-11-13 8:08 ` Ingo Molnar
2006-11-14 0:42 ` Andrew Morton [this message]
2006-11-14 6:46 ` Ingo Molnar
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=20061113164256.805a7497.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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
all inboxes | Powered by JetHome®