netdev - Re: [PATCH net 1/1] r8169: enforce RX_MULTI

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20130912.024041.1357115695225954085.davem@davemloft.net>
Date:	Thu, 12 Sep 2013 02:40:41 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	romieu@...zoreil.com
Cc:	dborkman@...hat.com, netdev@...r.kernel.org, david@...olicited.net,
	fredo@...rox.org, hayeswang@...ltek.com
Subject: Re: [PATCH net 1/1] r8169: enforce RX_MULTI_EN for the 8168f.

From: Francois Romieu <romieu@...zoreil.com>
Date: Thu, 12 Sep 2013 01:15:43 +0200

> David Miller <davem@...emloft.net> :
> [...]
>> Francois, if you reply to this thread with your signoff, all will
>> be well and I will apply this.
> 
> Signed-off-by: Francois Romieu <romieu@...zoreil.com>
> 
> I slowly built an AMD IOMMU + 8168{e/f} problem report pattern but
> the picture got blurred:
> - Hayes has not heard of anything like this
> - the oracle suggests it could be an "AMD IOMMU + whatever" problem
> - "iommu=pt" seems quite effective (hardly surprizing :o/ )
> 
> I still have a pile of iommu mailing-list messages to search through.
> Let aside the AMD-Vi error log message, I haven't done a thorough analysis.
> 
> It's lame.

Understood.  There were always IOMMU chips that sometimes prefetch one
cacheline too far (and thus potentially to the next page, which is
potentially unmapped) in certain circumstances.  Maybe these settings
trigger that kind of thing.

Applied and queued up for -stable, thanks.
--
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