All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Riley Williams" <Riley@Williams.Name>
To: "Linus Torvalds" <torvalds@transmeta.com>, <davidm@hpl.hp.com>
Cc: <roland@redhat.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] FIXMAP-related change to mm/memory.c
Date: Fri, 13 Jun 2003 08:28:47 +0100	[thread overview]
Message-ID: <BKEGKPICNAKILKJKMHCAIEALEFAA.Riley@Williams.Name> (raw)
In-Reply-To: <Pine.LNX.4.44.0306122219580.2989-100000@home.transmeta.com>

Hi Linus, all.

 >> Is it possible to constrain the FIXADDR range on x86/x86-64
 >> (FIXADDR_START-FIXADDR_TOP) such that the entire range is
 >> read-only by user-level?  If so, we could simplify the
 >> permission test like this:

 > Well, you could replace the uses of FIXADDR_START/FIXADDR_TOP
 > with something like FIXADDR_USER_START/FIXADDR_USER_TOP, and
 > then force those to cover only the _one_ user-accessible page.
 >
 > Something like
 >
 >	#define FIXADDR_USER_START (fix_to_virt(FIX_VSYSCALL))
 >	#define FIXADDR_USER_END (FIXADDR_USER_START + PAGE_SIZE)
 >
 > should work. In that case you can drop the page table testing,
 > since we "know" it is safe.

Should FIXADDR_USER_END point to the last byte of the relevant page,
or to the first byte of the following page as per Linus's suggestion?
The above looks like an off-by-one bug to me?

Best wishes from Riley.
---
 * Nothing as pretty as a smile, nothing as ugly as a frown.

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.488 / Virus Database: 287 - Release Date: 5-Jun-2003


      reply	other threads:[~2003-06-13  7:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-13  1:24 FIXMAP-related change to mm/memory.c David Mosberger
2003-06-13  2:07 ` Roland McGrath
2003-06-13  2:16   ` David Mosberger
2003-06-13  6:34     ` Roland McGrath
2003-06-13  6:37       ` David Mosberger
2003-06-13  6:56         ` Roland McGrath
2003-06-13  7:15           ` Andrew Morton
2003-06-15  6:51             ` Anton Blanchard
2003-06-13  7:17           ` David Mosberger
2003-06-13  5:24 ` Linus Torvalds
2003-06-13  7:28   ` Riley Williams [this message]

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=BKEGKPICNAKILKJKMHCAIEALEFAA.Riley@Williams.Name \
    --to=riley@williams.name \
    --cc=davidm@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@redhat.com \
    --cc=torvalds@transmeta.com \
    /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.