On Fri, 2005-08-12 at 22:35 +0200, Martijn van Oosterhout wrote:
> I had this problem when writing a kernel module that was using a UDP
> socket to send and receive stuff. It would work fine in UML but fail in
> the real kernel. I never worked it out but someone later patched it by
> using the
On Fri, Aug 12, 2005 at 11:16:23AM -0700, KrnlUsr wrote:
> Hi
>
> Why does copy_from/to_user routines fail if both
> source and destination are in kernel space. I have a
> kernel module that:
I had this problem when writing a kernel module that was using a UDP
socket to send and receive stuff.
Hi
Why does copy_from/to_user routines fail if both
source and destination are in kernel space. I have a
kernel module that:
1. takes some parameters from user space via ioctl
(kernel copies arguments with copy_from_user)
2. processes command(s) from user and
3. returns output to user with
On Fri, Aug 12, 2005 at 11:16:23AM -0700, KrnlUsr wrote:
> have the core routines copy processed data back to
> kernel thread or user space with copy_to_user. or do i
> have to have some check saying if called from ioctl
> call copy_to_user otherwise call memcpy?
Why wouldn't you just let the
On Fri, Aug 12, 2005 at 11:16:23AM -0700, KrnlUsr wrote:
have the core routines copy processed data back to
kernel thread or user space with copy_to_user. or do i
have to have some check saying if called from ioctl
call copy_to_user otherwise call memcpy?
Why wouldn't you just let the core
Hi
Why does copy_from/to_user routines fail if both
source and destination are in kernel space. I have a
kernel module that:
1. takes some parameters from user space via ioctl
(kernel copies arguments with copy_from_user)
2. processes command(s) from user and
3. returns output to user with
On Fri, Aug 12, 2005 at 11:16:23AM -0700, KrnlUsr wrote:
Hi
Why does copy_from/to_user routines fail if both
source and destination are in kernel space. I have a
kernel module that:
I had this problem when writing a kernel module that was using a UDP
socket to send and receive stuff. It
On Fri, 2005-08-12 at 22:35 +0200, Martijn van Oosterhout wrote:
I had this problem when writing a kernel module that was using a UDP
socket to send and receive stuff. It would work fine in UML but fail in
the real kernel. I never worked it out but someone later patched it by
using the
8 matches
Mail list logo
