* Q: which archs differ between VERIFY_READ and VERIFY_WRITE in access_ok?
@ 2003-04-21 20:25 Manfred Spraul
0 siblings, 0 replies; only message in thread
From: Manfred Spraul @ 2003-04-21 20:25 UTC (permalink / raw)
To: linux-kernel
I noticed that access_ok receives a flag that specifies read or write
access.
Do any archs rely on that flag, except 80386?
For example sys_poll contains:
> if (copy_from_user(pp->entries, ufds + nfds-i,
> sizeof(struct pollfd)*pp->len)) {
> err = -EFAULT;
> goto out_fds;
> }
> i -= pp->len;
>
>
[snip: code that allocates memory, sleep until data is around, ...]
> if(__put_user(fds[j].revents, &ufds->revents))
> goto out_fds;
>
>
If an arch really treats VERIFY_READ differently that VERIFY_WRITE, then
this would be wrong.
Are there ports that perform some checks only for VERIFY_WRITE? I have a
fix for 80386.
--
Manfred
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-04-21 20:13 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-04-21 20:25 Q: which archs differ between VERIFY_READ and VERIFY_WRITE in access_ok? Manfred Spraul
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox