On 02/15/2013 04:22 PM, Dutta Yashpal-B05456 wrote:
> Hi Phil,
>
> This can break because copy_from/to_user() copies from the current user
> process (which should be obvious, since
> there's no way to tell it which user process to copy from).
>
> In a syscall invoked by your userspace process
Hello Yashpal,
On Fri, Feb 15, 2013 at 03:22:54PM +, Dutta Yashpal-B05456 wrote:
> This can break because copy_from/to_user() copies from the current user
> process (which should be obvious, since
> there's no way to tell it which user process to copy from).
>
> In a syscall invoked by your
From: cryptodev-linux-devel-boun...@gna.org [mailto:cryptodev-linux-
> devel-boun...@gna.org] On Behalf Of Phil Sutter
> Sent: Friday, February 15, 2013 6:42 AM
> To: cryptodev-linux-devel@gna.org
> Subject: Re: [Cryptodev-linux-devel] Asynchronous support in Cryptodev is
> buggy
>
Hi,
On Thu, Feb 14, 2013 at 05:20:07PM +, Dutta Yashpal-B05456 wrote:
> Looked at asynchronous support in Cryptodev-1.5 and found that it is getting
> in following flow
> cryptask_routine calling crypto_run. Now in crypto_run API, all the
> user-space process provided
> buffers are either b
Hi,
Looked at asynchronous support in Cryptodev-1.5 and found that it is getting in
following flow
cryptask_routine calling crypto_run. Now in crypto_run API, all the user-space
process provided
buffers are either being copied to kernel buffers or they are being mapped in
kernel using
get_use
