linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hillf Danton <dhillf@gmail.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: x86@kernel.org, Andrew Morton <akpm@linux-foundation.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>,
	Stefani Seibold <stefani@seibold.net>
Subject: Re: [PATCH v2 -next] x86,vdso: Fix an OOPS accessing the hpet mapping w/o an hpet
Date: Thu, 15 May 2014 11:18:29 +0800	[thread overview]
Message-ID: <CAJd=RBC1E9x-zU-zJbNP+zbPgb=nhi39TqrxqpcGdi=OR9duXg@mail.gmail.com> (raw)
In-Reply-To: <c8b0a9a0b8d011a8b273cbb2de88d37190ed2751.1400111179.git.luto@amacapital.net>

Hi Andy,

On Thu, May 15, 2014 at 7:46 AM, Andy Lutomirski <luto@amacapital.net> wrote:
> The oops can be triggered in qemu using -no-hpet (but not nohpet) by
> reading a couple of pages past the end of the vdso text.  This
> should send SIGBUS instead of OOPSing.
>
> The bug was introduced by:
>
> commit 7a59ed415f5b57469e22e41fc4188d5399e0b194
> Author: Stefani Seibold <stefani@seibold.net>
> Date:   Mon Mar 17 23:22:09 2014 +0100
>
>     x86, vdso: Add 32 bit VDSO time support for 32 bit kernel
>
> which is new in 3.15.
>
> This will be fixed separately in 3.15, but that patch will not apply
> to tip/x86/vdso.  This is the equivalent fix for tip/x86/vdso and,
> presumably, 3.16.
>
> Cc: Stefani Seibold <stefani@seibold.net>
> Reported-by: Sasha Levin <sasha.levin@oracle.com>
> Signed-off-by: Andy Lutomirski <luto@amacapital.net>
> ---
>  arch/x86/vdso/vma.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/x86/vdso/vma.c b/arch/x86/vdso/vma.c
> index e915eae..8ad0081 100644
> --- a/arch/x86/vdso/vma.c
> +++ b/arch/x86/vdso/vma.c
> @@ -90,6 +90,7 @@ static int map_vdso(const struct vdso_image *image, bool calculate_addr)
>         struct vm_area_struct *vma;
>         unsigned long addr;
>         int ret = 0;
> +       static struct page *no_pages[] = {NULL};
>
>         if (calculate_addr) {
>                 addr = vdso_addr(current->mm->start_stack,
> @@ -125,7 +126,7 @@ static int map_vdso(const struct vdso_image *image, bool calculate_addr)
>                                        addr + image->size,
>                                        image->sym_end_mapping - image->size,
>                                        VM_READ,
> -                                      NULL);
> +                                      no_pages);
>
>         if (IS_ERR(vma)) {
>                 ret = PTR_ERR(vma);
> --
> 1.9.0
>
As the comment says,
/*
 * Called with mm->mmap_sem held for writing.
 * Insert a new vma covering the given region, with the given flags.
 * Its pages are supplied by the given array of struct page *.
 * The array can be shorter than len >> PAGE_SHIFT if it's null-terminated.
 * The region past the last page supplied will always produce SIGBUS.
 * The array pointer and the pages it points to are assumed to stay alive
 * for as long as this mapping might exist.
 */
struct vm_area_struct *_install_special_mapping(struct mm_struct *mm,
   unsigned long addr, unsigned long len,
   unsigned long vm_flags, struct page **pages)
{

we can send sigbus at fault time if no pages are supplied at install time.

thanks
Hillf

--
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>

  reply	other threads:[~2014-05-15  3:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 23:46 Andy Lutomirski
2014-05-15  3:18 ` Hillf Danton [this message]
2014-05-15  3:38   ` Andrew Morton
2014-05-15  4:15     ` Hillf Danton

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='CAJd=RBC1E9x-zU-zJbNP+zbPgb=nhi39TqrxqpcGdi=OR9duXg@mail.gmail.com' \
    --to=dhillf@gmail.com \
    --cc=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=stefani@seibold.net \
    --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