linux-kernel - Re: [PATCH 0 of 28] ipath patches for 2.6.19

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:	Fri, 29 Sep 2006 18:36:25 -0600
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	"Bryan O'Sullivan" <bos@...hscale.com>
Cc:	rdreier@...co.com, linux-kernel@...r.kernel.org,
	openib-general@...nib.org
Subject: Re: [PATCH 0 of 28] ipath patches for 2.6.19

"Bryan O'Sullivan" <bos@...hscale.com> writes:

> Hi, Roland -
>
> This patch series brings the ipath driver almost up to date with what's
> in our internal tree.  The only substantial thing missing is the
> memcpy_cachebypass patch that I sent out a while back and haven't had
> time to rework.
>
> These patches have seen a lot of testing, including on a git snapshot
> as of yesterday afternoon.  Please apply.

Have you tested your driver against the -mm tree?

To the best of my knowledge the irq handling of your hypertransport card
is a complete and total hack that works only by chance.

In the -mm tree I have added a first pass at proper support for the
hypertranport interrupt capability.  As this code is slated to go into
2.6.19 could you please test against that?

I would have tested it myself except when I mentioned this earlier I was told
that your card does not actually implement the hypertransport interrupt
capability properly.  

The practical reason for pathscale to work on this is the genirq work
in 2.6.19 changes the internal implementation detail your
hypertransport card has been relying on to work so your hypertranport
card will not work without fixes.

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