netdev - RE: [PATCH net 1/4] pegasus: Use heap buffers for all register access

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]

Message-ID: <063D6719AE5E284EB5DD2968C1650D6DB027C7C7@AcuExch.aculab.com>
Date:   Mon, 6 Feb 2017 13:30:11 +0000
From:   David Laight <David.Laight@...LAB.COM>
To:     'Petko Manolov' <petkan@...leusys.com>, Greg KH <greg@...ah.com>
CC:     Ben Hutchings <ben@...adent.org.uk>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
        Lisandro Damián Nicanor Pérez Meyer 
        <lisandro@...ian.org>
Subject: RE: [PATCH net 1/4] pegasus: Use heap buffers for all register
 access

From: Petko Manolov
> Sent: 06 February 2017 12:51
...
> I suspect getting the buffer allocation in usb_control_msg() will help with two
> things in the same time:
> 
>  - allocate in DMA-able memory;
>  - code reduction;

Is there code around there to do 'bounce buffer' allocation
for systems where not all dma memory is actually accessible
by all devices??

In which case it could (probably) be used for non-dma memory?

	David