Re: MMAP: How a driver can get called on mprotect()

> Well, what hardware is it for and where can we download the driver to
> have a view at it? That'd probably help suggesting something...
>

Well actually is a virtual memory driver somewhat based on scullp
device in the book Linux Device Drivers 3rd edition.

Nonetheless the question is the same: a char device with mmap
implemented can get called any time a new vma is created or destroyed
(a process creating a new mmap):  vma_open() and vma_close().

But if a user process changes the mmap protections calling mprotect()?
How can the driver know about that? Is there any way to do that?

Thanks
-
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/

Follow-Ups:
- Re: MMAP: How a driver can get called on mprotect()
  - From: Brice Goglin <[email protected]>

References:
- MMAP: How a driver can get called on mprotect()
  - From: "Aritz Bastida" <[email protected]>
- Re: MMAP: How a driver can get called on mprotect()
  - From: Jan-Benedict Glaw <[email protected]>

Prev by Date: Re: MMAP: How a driver can get called on mprotect()
Next by Date: Re: libata PATA patch for 2.6.16-rc5
Previous by thread: Re: MMAP: How a driver can get called on mprotect()
Next by thread: Re: MMAP: How a driver can get called on mprotect()
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]