Re: [PATCH 10/17] BLOCK: Move the loop device ioctl compat stuff to the loop driver [try #2]

Arnd Bergmann <[email protected]> wrote:

> My idea was to do the copy_from_user in loop_set_status_compat instead
> of loop_info64_from_compat, but your solution should be completely
> equivalent.

This way will have used less stack when it gets to the main part of the loop
driver.

David
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [PATCH 10/17] BLOCK: Move the loop device ioctl compat stuff to the loop driver [try #2]
  - From: David Howells <[email protected]>
- Re: [PATCH 10/17] BLOCK: Move the loop device ioctl compat stuff to the loop driver [try #2]
  - From: David Howells <[email protected]>

Prev by Date: Re: Serial custom speed deprecated?
Next by Date: Re: T60 not coming out of suspend to RAM
Previous by thread: Re: [PATCH 10/17] BLOCK: Move the loop device ioctl compat stuff to the loop driver [try #2]
Next by thread: [PATCH 11/17] BLOCK: Move common FS-specific ioctls to linux/fs.h [try #2]
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]