From: Manfred Spraul <manfred@colorfullife.com>
To: linux-kernel@vger.kernel.org
Subject: Q: which archs differ between VERIFY_READ and VERIFY_WRITE in access_ok?
Date: Mon, 21 Apr 2003 22:25:35 +0200 [thread overview]
Message-ID: <3EA453BF.7030206@colorfullife.com> (raw)
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
reply other threads:[~2003-04-21 20:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3EA453BF.7030206@colorfullife.com \
--to=manfred@colorfullife.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox