linux-kernel - Re: 2.6.19-rc4: known unfixed regressions (v3)

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:	Tue, 7 Nov 2006 05:22:14 +0100
From:	Adrian Bunk <bunk@...sta.de>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Bryan O'Sullivan <bos@...pentine.com>
Subject: Re: 2.6.19-rc4: known unfixed regressions (v3)

On Sun, Nov 05, 2006 at 08:17:53AM -0700, Eric W. Biederman wrote:
> Adrian Bunk <bunk@...sta.de> writes:
> 
> > This email lists some known regressions in 2.6.19-rc4 compared to 2.6.18
> > that are not yet fixed in Linus' tree.
> >
> > If you find your name in the Cc header, you are either submitter of one
> > of the bugs, maintainer of an affectected subsystem or driver, a patch
> > of you caused a breakage or I'm considering you in any other way possibly
> > involved with one or more of these issues.
> >
> > Due to the huge amount of recipients, please trim the Cc when answering.
> >
> >
> > Subject    : ipath driver MCEs system on load when HT chip present
> > References : http://bugzilla.kernel.org/show_bug.cgi?id=7455
> > Submitter  : Bryan O'Sullivan <bos@...pentine.com>
> > Caused-By  : Eric W. Biederman <ebiederm@...ssion.com>
> > Status     : unknown
> 
> Status in problem is being debugged. I have posted some infrastructure
> patches that should allow Bryan to fix his driver cleanly.  
> 
> I did not cause this. The ipath HTX card driver's irq handling has
> never been anything but a hack.  It has never worked correctly even in
> the instances it worked.  It only worked on i386 or x86_64 when
> CONFIG_PCI_MSI was enabled but did not use MSI.  It was relying on the
> implementation detail that the architecture specific vector number was
> placed in the dev->irq.  dev->irq is actually meaningless on this card
> as it doesn't have any ordinary pci interrupts.
> 
> So while I am happy to take credit for flushing this bug out I did not
> introduce it.

My notion of "regression" is from a user's perspective.

Therefore, if a hack that worked at least for some users no longer 
works, that's a regression. That's independent of the technical question 
whose fault it actually was.

We should either get this fixed before 2.6.19 or at least make it clear 
for users that support for this hardware won't be back before 2.6.20.

> Eric

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

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