All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Venki Pallipadi <venkatesh.pallipadi@intel.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	arjan@linux.intel.com,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add range_is_allowed() check to mmap of /dev/mem
Date: Fri, 7 Mar 2008 09:37:54 +0100	[thread overview]
Message-ID: <20080307083754.GD12150@elte.hu> (raw)
In-Reply-To: <20080307070147.GA9888@linux-os.sc.intel.com>


* Venki Pallipadi <venkatesh.pallipadi@intel.com> wrote:

> Earlier patch that introduced CONFIG_NONPROMISC_DEVMEM, did the 
> range_is_allowed() check only for read and write. Add 
> range_is_allowed() check to mmap of /dev/mem as well.
> 
> Changes the paramaters of range_is_allowed() to pfn and size to handle 
> more than 32 bits of physical address on 32 bit arch cleanly.

thanks, applied.

	Ingo

      reply	other threads:[~2008-03-07  8:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07  7:01 [PATCH] Add range_is_allowed() check to mmap of /dev/mem Venki Pallipadi
2008-03-07  8:37 ` Ingo Molnar [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=20080307083754.GD12150@elte.hu \
    --to=mingo@elte.hu \
    --cc=arjan@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=venkatesh.pallipadi@intel.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.