From: "Aritz Bastida" <aritzbastida@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: "Jan-Benedict Glaw" <jbglaw@lug-owl.de>
Subject: Re: MMAP: How a driver can get called on mprotect()
Date: Sun, 5 Mar 2006 19:40:18 +0100 [thread overview]
Message-ID: <7d40d7190603051040h17da06caw@mail.gmail.com> (raw)
In-Reply-To: <20060305182240.GH19232@lug-owl.de>
> 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
next prev parent reply other threads:[~2006-03-05 18:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-05 18:12 MMAP: How a driver can get called on mprotect() Aritz Bastida
2006-03-05 18:22 ` Jan-Benedict Glaw
2006-03-05 18:40 ` Aritz Bastida [this message]
2006-03-05 20:18 ` Brice Goglin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7d40d7190603051040h17da06caw@mail.gmail.com \
--to=aritzbastida@gmail.com \
--cc=jbglaw@lug-owl.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.