Messages in this thread | | | Date | Mon, 11 Mar 2013 20:51:25 +0000 | From | Chris Wilson <> | Subject | Re: [PATCH] drm/i915: clarify reasoning for the access_ok call |
| |
On Mon, Mar 11, 2013 at 12:26:30PM -0700, Kees Cook wrote: > This clarifies the comment above the access_ok check so a missing > VERIFY_READ doesn't alarm anyone.
Do we really need to copy the interface documentation?
/** * access_ok: - Checks if a user space pointer is valid * @type: Type of access: %VERIFY_READ or %VERIFY_WRITE. Note that * %VERIFY_WRITE is a superset of %VERIFY_READ - if it is safe * to write to a block, it is always safe to read from it. * @addr: User space pointer to start of block to check * @size: Size of block to check */ -Chris
-- Chris Wilson, Intel Open Source Technology Centre
| |