linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: x86@kernel.org, Sasha Levin <sasha.levin@oracle.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Dave Jones <davej@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3.15] x86,vdso: Fix an OOPS accessing the hpet mapping w/o an hpet
Date: Wed, 14 May 2014 16:16:30 -0700	[thread overview]
Message-ID: <20140514161630.d604884474d13a4432360b0f@linux-foundation.org> (raw)
In-Reply-To: <e1640272803e7711d9a43d9454dbdae57ba22eed.1400108299.git.luto@amacapital.net>

On Wed, 14 May 2014 16:01:22 -0700 Andy Lutomirski <luto@amacapital.net> wrote:

> The access should fail, but it shouldn't oops.
> 
> Signed-off-by: Andy Lutomirski <luto@amacapital.net>
> ---
> 
> The oops can be triggered in qemu using -no-hpet (but not nohpet) by
> running a 32-bit program and reading a couple of pages before the vdso.

This sentence is the best part of the changelog!  People often do this
- they put all the good stuff after the ^---.  I always move it into
the changelog.

So how old is this bug?

> --- a/arch/x86/vdso/vdso32-setup.c
> +++ b/arch/x86/vdso/vdso32-setup.c
> @@ -147,6 +147,8 @@ int __init sysenter_setup(void)
>  	return 0;
>  }
>  
> +static struct page *no_pages[] = {NULL};

nit: this could be local to arch_setup_additional_pages().

>  /* Setup a VMA at program startup for the vsyscall page */
>  int arch_setup_additional_pages(struct linux_binprm *bprm, int uses_interp)
>  {
> @@ -192,7 +194,7 @@ int arch_setup_additional_pages(struct linux_binprm *bprm, int uses_interp)
>  			addr -  VDSO_OFFSET(VDSO_PREV_PAGES),
>  			VDSO_OFFSET(VDSO_PREV_PAGES),
>  			VM_READ,
> -			NULL);
> +			no_pages);
>  
>  	if (IS_ERR(vma)) {
>  		ret = PTR_ERR(vma);

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2014-05-14 23:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 23:01 Andy Lutomirski
2014-05-14 23:01 ` [PATCH] " Andy Lutomirski
2014-05-14 23:16 ` Andrew Morton [this message]
2014-05-14 23:18   ` [PATCH 3.15] " Andy Lutomirski

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=20140514161630.d604884474d13a4432360b0f@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@amacapital.net \
    --cc=sasha.levin@oracle.com \
    --cc=x86@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