linux-kernel - Re: [Bug #11201] kernel BUG at arch/x86/kernel/io_apic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <m1wsior6lk.fsf@frodo.ebiederm.org>
Date:	Sun, 10 Aug 2008 12:51:51 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	Dhaval Giani <dhaval@...ux.vnet.ibm.com>,
	Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: [Bug #11201] kernel BUG at arch/x86/kernel/io_apic_64.c:357!

"H. Peter Anvin" <hpa@...or.com> writes:

> Eric W. Biederman wrote:
>> "Rafael J. Wysocki" <rjw@...k.pl> writes:
>>
>>> This message has been generated automatically as a part of a report
>>> of recent regressions.
>>>
>>> The following bug entry is on the current list of known regressions
>>> from 2.6.26.  Please verify if it still should be listed and let me know
>>> (either way).
>>
>> Yep.  There is a patch in -mm.  It seems the process is to wait for Thomas &
>> Ingo to get back before we send this to Linus.
>>
>
> Yes, unfortunately I still don't have enough testing resources to want to push
> this upstream.  I'm queuing it up for submission, though.

No problem.  I don't expect any problems as it is a simple reversion of the
definition of NR_IRQS on x86_64 to what we had before everything was merged
into irq_vectors.h and the x86_64 bits got lost.

With the result that NR_IRQS varies in practice between 244 and 4096
depending on how many cpus you have.  We have had NR_IRQS that large on
x86_64 for a year or better now so I don't expect any practical problems.

The long term fix will obviously be kill NR_IRQS.  But that is not a 2.6.27
term project.

Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/