linux-kernel - Re: [HOWTO] accessing the DMA mapped data

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:	Thu, 10 May 2007 04:32:33 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	maheshk@...c.in
Cc:	linux-kernel@...r.kernel.org, kernelnewbies@...linux.org
Subject: Re: [HOWTO] accessing the DMA mapped data

From: Mahesh <maheshk@...c.in>
Date: Thu, 10 May 2007 16:49:03 +0530

> I think you have not understood my question properly. My problem is, the 
> layer above the driver will do
> dma_map_single on a kmalloc'ed buffer and passes the result  (bus 
> address) to the device driver. Now
> the driver has to modify the contents of the the original buffer.
> Is it possible to do that ??

You haven't given an example of where this might actually happen.

The driver is where the DMA mappings almost always occur because
that is the layer that knows the bus technology and therefore
the correct DMA interfaces to call.

What kind of driver do you have and what is this upper layer
doing the mappings for you but not giving you a pointer to
the kernel buffer as well?
-
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/