netdev - Re: [PATCH] 2.6.27-rc9 QGLE make unsupported page size explicit compile failure

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:	Mon, 13 Oct 2008 20:19:02 -0600
From:	Matthew Wilcox <matthew@....cx>
To:	David Miller <davem@...emloft.net>
Cc:	ron.mercer@...gic.com, grundler@...isc-linux.org,
	linux-driver@...gic.com, netdev@...r.kernel.org,
	linux-ia64@...r.kernel.org
Subject: Re: [PATCH] 2.6.27-rc9 QGLE make unsupported page size explicit compile failure

On Mon, Oct 13, 2008 at 07:03:45PM -0700, David Miller wrote:
> From: Ron Mercer <ron.mercer@...gic.com>
> Date: Mon, 13 Oct 2008 18:54:55 -0700
> 
> > This ASIC does support all page sizes. For 4k and 8k page size the TX control block needs an external scatter gather list.  For page sizes larger than 8k the max frags is satisfied by the original TX control block.
> 
> I'm not applying this.  I _explicitly_ said I would not apply a
> solution like this.
> 
> I waited for you guys all day for this?!?!
> 
> We need to find a way to make this a Kconfig dependency.
> 
> Build failures are absolutely unacceptable.

Um, Dave, I think you misread his patch.

All it does it make the '64k case' the 'every other size case'.  There's
no build failure with Ron's patch.

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html