linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Vladimir Murzin <murzin.v@gmail.com>
Cc: linux-arch@vger.kernel.org, tglx@linutronix.de,
	davem@davemloft.net, lethal@linux-sh.org
Subject: Re: [PATCH 0/6] get rid of extra check for TASK_SIZE in get_unmapped_area
Date: Wed, 9 May 2012 17:26:57 +0100	[thread overview]
Message-ID: <20120509162657.GC10241@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1336488022-3723-1-git-send-email-murzin.v@gmail.com>

On Tue, May 08, 2012 at 06:40:16PM +0400, Vladimir Murzin wrote:
> From: Vladimir Murzin <murzin.v@gmail>
> 
> The current get_unmapped_area code calls the f_ops->get_unmapped_area or
> the arch's one (via the mm) only when check for TASK_SIZE is passed. However,
> generic code and some arches do the same check in their a_g_u_a implementation.
> 
> This series of patches fix the check order for TASK_SIZE in archs'
> get_unmapped_area() implementations, and then removes extra check in
> high-level get_unmapped_area().

Do we even need this check in arch code?  AFAICS it's already checked in
get_unmapped_area(), and this will be called prior to any
arch_get_unmapped_area() implementation.  Given that this is a potential
security issue, please check my analysis of this.

unsigned long
get_unmapped_area(struct file *file, unsigned long addr, unsigned long len,
		unsigned long pgoff, unsigned long flags)
{
	...
	/* Careful about overflows.. */
	if (len > TASK_SIZE)
		return -ENOMEM;

	get_area = current->mm->get_unmapped_area;
	if (file && file->f_op && file->f_op->get_unmapped_area)
		get_area = file->f_op->get_unmapped_area;

  parent reply	other threads:[~2012-05-09 16:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08 14:40 [PATCH 0/6] get rid of extra check for TASK_SIZE in get_unmapped_area Vladimir Murzin
2012-05-08 14:40 ` [PATCH 1/6] get_unmapped_area checks for TASK_SIZE before MAP_FIXED on arm Vladimir Murzin
2012-05-08 14:40 ` [PATCH 2/6] get_unmapped_area checks for TASK_SIZE before MAP_FIXED on sh Vladimir Murzin
2012-05-08 14:40 ` [PATCH 3/6] get_unmapped_area checks for TASK_SIZE before MAP_FIXED on sparc32 Vladimir Murzin
2012-05-08 16:27   ` Sam Ravnborg
2012-05-09  8:07     ` Vladimir Murzin
2012-05-09 16:18       ` Sam Ravnborg
2012-05-09 18:04         ` Vladimir Murzin
2012-05-08 17:00   ` David Miller
2012-05-08 14:40 ` [PATCH 4/6] get_unmapped_area checks for TASK_SIZE before MAP_FIXED on sparc64 Vladimir Murzin
2012-05-08 17:00   ` David Miller
2012-05-08 14:40 ` [PATCH 5/6] get_unmapped_area checks for TASK_SIZE before MAP_FIXED on x86_64 Vladimir Murzin
2012-05-08 14:40 ` [PATCH 6/6] get_unmapped_area remove extra check for TASK_SIZE Vladimir Murzin
2012-05-09 16:26 ` Russell King - ARM Linux [this message]
2012-05-09 17:56   ` [PATCH 0/6] get rid of extra check for TASK_SIZE in get_unmapped_area Vladimir Murzin
2012-05-09 18:07     ` Russell King - ARM Linux
2012-05-10  3:01       ` Vladimir Murzin
2012-05-10  7:55         ` Russell King - ARM Linux
2012-05-10 18:08           ` Vladimir Murzin

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=20120509162657.GC10241@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=davem@davemloft.net \
    --cc=lethal@linux-sh.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=murzin.v@gmail.com \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).