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]
Date:	Sun, 27 Nov 2011 12:22:54 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>
Cc:	Dave Airlie <airlied@...il.com>, linux-kernel@...r.kernel.org,
	drivers_pci@...nel-bugs.osdl.org,
	Rogério Brito <rbrito@....usp.br>
Subject: Re: [Bug 41132] [BISECTED][REGRESSION] Regression with the IRQ
 subsystem introduced in 2.6.39 (and present in the 3.x version)

Thomas, Ingo?

I haven't seen any response to this one, and while clearly commit
fa27271bc8d2 ("genirq: Fixup poll handling") was *supposed* to be a
no-op, it isn't.

The commit message says "Shorter version with the same
functionality.", but since it causes a regression, it clearly is not
with the same functionality at all. And I assume that Thomas doesn't
have a machine that actually ever triggers the spurious irq issue to
begin with, so it probably was never tested.

In short, it really sounds like this should just be reverted, since
the code clearly doesn't do what the commit message claims it does.

Comments?

              Linus

2011/11/22 Rogério Brito <rbrito@....usp.br>:
> Hi there.
>
> Now that, at least part of kernel.org is up, I would appreciate if
> more people could help with debugging something that I reported to
> bugzilla in july of this year, a regression (bisected) that led to a
> bad commit of Thomas in the 2.6.39 cycle as the first bad one.
>
> Bugzilla has more information on the issue, but as it seems to be
> down, I can, of course, summarize what I found. And, unfortunately,
> the problem still occurs with a recent pull of Linus tree up to
> v3.2-rc2-43-gaa1b052.
>
> Below is the link to my first message that was archived:
>
>> --- Comment #3 from Rogério Brito <rbrito@....usp.br>  2011-08-16 05:54:47 ---
>> Add note that this bug was first reported on 2011-07-04
>>
>>    https://lkml.org/lkml/2011/7/24/54
>>
>> As stated on that e-mail, I am willing to perform any tests to help fix this
>> bug. Just ask me and I will do my best to give you copious amounts of data.
>
>
> Thanks,
> Rogério Brito.
>
> --
> Rogério Brito : rbrito@...e.usp.br,gmail.com} : GPG key 4096R/BCFCAAAA
> http://rb.doesntexist.org : Packages for LaTeX : algorithms.berlios.de
> DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
>
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ