as a followup to my earlier note, i was checking on the
implementation of the access_ok() routine which checks the validity of
user-space access from the kernel and, for x86_64, it's defined as:
#define access_ok(type, addr, size) \
(likely(__range_not_ok(addr, size) == 0))
as you can see, the "type" arg is unused in the macro definition, and
that's normally where you would expect to find either VERIFY_READ or
VERIFY_WRITE.
i perused that macro for all other architectures and it seems that
that first argument is entirely unused these days. is that just
historical leftovers? or am i missing something?
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ
