netdev - RE: [PATCH v2 0/2] pegasus: correct buffer sizes

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

Message-ID: <063D6719AE5E284EB5DD2968C1650D6D5F4ABB06@AcuExch.aculab.com>
Date:	Wed, 27 Apr 2016 16:26:49 +0000
From:	David Laight <David.Laight@...LAB.COM>
To:	'Johannes Berg' <johannes@...solutions.net>,
	Petko Manolov <petkan@...-labs.com>
CC:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"davem@...emloft.net" <davem@...emloft.net>,
	"a1291762@...il.com" <a1291762@...il.com>
Subject: RE: [PATCH v2 0/2] pegasus: correct buffer sizes

From: Johannes Berg
> Sent: 27 April 2016 10:44
> On Wed, 2016-04-27 at 12:33 +0300, Petko Manolov wrote:
> >
> > Your guess turned out to be not so wild.;)All Pegasus devices are
> > configured (by the driver) to append CRC at the end of each RX
> > packet.However, the driver reports packet length that does not
> > include it.
> 
> Interesting, then my guess was wrong though, since the length is
> reported without it, or am I misunderstanding this?
...

It is even possible that the crc is written into the rx buffer even
though the length the hardware reports excludes it.

	David