linux-kernel - Re: Strange network timeouts w/ 2.6.30.5

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-next>] [day] [month] [year] [list]

Date:	Fri, 21 Aug 2009 10:45:04 -0500 (CDT)
From:	Walt Holman <walt@...mansrus.com>
To:	Krzysztof Halasa <khc@...waw.pl>
Cc:	David Miller <davem@...emloft.net>, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: Strange network timeouts w/ 2.6.30.5


----- "Krzysztof Halasa" <khc@...waw.pl> wrote:

> Walt Holman <walt@...mansrus.com> writes:
> 
> > Would something like passing a mem=xx cmdline on x86_64 be
> sufficient to test this?
> 
> I think so, though I admit I don't remember using this personally
> since
> the introduction of e820 RAM mapping support.
> Dmesg will show if the memory is limited. For the swiotlb to
> effectively
> disable no RAM > 0x100000000 may be used.
> 
> But this test isn't IMHO terribly important at this point - the
> driver
> makes invalid use of the DMA API and it has to change. The test could
> only explain _how_ exactly does it fail, we already know _why_ it
> does.
> -- 
> Krzysztof Halasa

Just got a chance to test this for confirmation.  When limiting the RAM to 2GB, the patched driver appears to work OK.

-Walt

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