linux-kernel - Re: 2.6.{30,31} x86_64 ahci problem

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: <4ABBCACE.90506@caviumnetworks.com>
Date:	Thu, 24 Sep 2009 12:38:54 -0700
From:	David Daney <ddaney@...iumnetworks.com>
To:	Alexander Huemer <alexander.huemer@....ac.at>
CC:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.{30,31} x86_64 ahci problem - irq 23: nobody cared

Alexander Huemer wrote:
> David Daney wrote:
>> Alexander Huemer wrote:
>>> the problem appears under heavy system load and slows down the system to
>>> unusable speed.
>>> kernels before .30 were not affected.
>>> irqpoll does not change behavior.
>>>
>>> error message from .31:
>>>
>>>     [157152.418524] irq 23: nobody cared (try booting with the "irqpoll"
>>>     option)
>>>     [157152.418530] Pid: 1359, comm: cc1plus Tainted: G        W 
>> Right here is the problem  ->         ^^^^^^^^
>>
>> Haven't you read all the threads about the evil of C++.  This is just
>> one more example of the why we shouldn't be using it. :-)
>>
>> David Daney
>>
[...]
> thanks for your quick answer, david.
> so, this isn't a kernel issue at all ?
> imho a user process shouldn't be able to cause such a situation.
> what can i do against that phenomenon ?
> 

Just for avoidance of doubt, it was an attempt at a joke.

You are of course correct.  It looks like a real bug.  User-space 
shouldn't matter.

David Daney
--
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/