All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Stefani Seibold <stefani@seibold.net>
Cc: Andy Lutomirski <luto@amacapital.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andreas Brief <Andreas.Brief@rohde-schwarz.com>,
	Martin Runge <Martin.Runge@rohde-schwarz.com>
Subject: Re: [x86, vdso] BUG: unable to handle kernel paging request at d34bd000
Date: Mon, 10 Mar 2014 16:02:32 -0700	[thread overview]
Message-ID: <531E4488.2000400@linux.intel.com> (raw)
In-Reply-To: <CA+55aFygdFWCVzsSNT6v-8Mnsq8rrFwz0d1ydOLRthv4JsBaBQ@mail.gmail.com>

On 03/10/2014 02:39 PM, Linus Torvalds wrote:
> On Mon, Mar 10, 2014 at 2:25 PM,  <stefani@seibold.net> wrote:
>>
>> This was discovered by me.
> 
> Sorry for the misattribution.
> 
>> But this is not a real solution, at least when vcpu function support
>> will be added, then the code size will exceed the page size. Reserving
>> two pages for the VDSO is a good option.
> 
> Quite frankly, there is no way in hell I will take a patch like that
> for 3.14 any more, and I would argue against it for stable.
> 
> Now, if this problem never happens with current kernels (because it's
> purely due to the patch in -tip), then I don't much care.
> 

It is only for tip:x86/vdso, so current kernels don't matter.

There is going to be 32-bit use in the embedded sector for a long time
to come, I suspect/fear, so I'm not opposed to giving it a bit of a
performance boost as long as it isn't too invasive.

I think Andy's commentary applies, though :)

> IMO this is dumb.  I can think of two sensible solutions:
> 
> 1. Get rid of compat vdso and replace it with no vdso at all.  This is
> compatible with everything and requires almost no code 
> 
> 2. Fix compat vdso.  Give it as much space as needed, make the address
> dynamic, and relocate it to the right place.


	-hpa


  parent reply	other threads:[~2014-03-10 23:04 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-07  1:38 [x86, vdso] BUG: unable to handle kernel paging request at d34bd000 Fengguang Wu
2014-03-07  1:48 ` [x86, vdso] BUG: unable to handle kernel paging request at 91c24000 Fengguang Wu
2014-03-07  7:21 ` [x86, vdso] BUG: unable to handle kernel paging request at d34bd000 Stefani Seibold
2014-03-07 18:56   ` Andy Lutomirski
2014-03-07 21:53     ` Stefani Seibold
2014-03-07 23:07       ` Andy Lutomirski
2014-03-09  8:47         ` Stefani Seibold
2014-03-10  0:16           ` H. Peter Anvin
2014-03-10  3:18             ` Andy Lutomirski
2014-03-10  4:46               ` Andy Lutomirski
2014-03-10 14:59                 ` H. Peter Anvin
     [not found]                   ` <CA+55aFwKpBybz9S9A=+tcr1BbdzAbagL30Br2cak2GrdPH=hhA@mail.gmail.com>
2014-03-10 17:12                     ` Andy Lutomirski
2014-03-10 17:24                       ` H. Peter Anvin
2014-03-10 17:31                         ` Andy Lutomirski
2014-03-10 17:38                           ` H. Peter Anvin
2014-03-10 17:46                             ` Andy Lutomirski
2014-03-10 17:48                               ` H. Peter Anvin
2014-03-10 17:52                                 ` Andy Lutomirski
2014-03-10 17:58                                   ` H. Peter Anvin
2014-03-10 18:10                                     ` Andy Lutomirski
2014-03-10 17:49                               ` H. Peter Anvin
2014-03-10 20:03                       ` Stefani Seibold
2014-03-10 20:06                         ` H. Peter Anvin
2014-03-10 20:19                           ` Linus Torvalds
2014-03-10 21:20                             ` Linus Torvalds
2014-03-10 21:43                               ` Andy Lutomirski
2014-03-10 21:51                               ` Dave Jones
2014-03-10 22:59                                 ` H. Peter Anvin
2014-03-10 23:32                                   ` [PATCH] x86: Remove CONFIG_X86_OOSTORE Dave Jones
2014-03-11 10:11                               ` [x86, vdso] BUG: unable to handle kernel paging request at d34bd000 Ingo Molnar
2014-03-10 21:25                             ` stefani
2014-03-10 21:39                               ` Linus Torvalds
2014-03-10 21:53                                 ` stefani
2014-03-10 22:03                                   ` Andy Lutomirski
2014-03-10 22:36                                     ` Andy Lutomirski
2014-03-10 23:02                                 ` H. Peter Anvin [this message]
2014-03-10 21:29                           ` stefani
2014-03-11  6:02                             ` H. Peter Anvin
2014-03-07  8:47 ` Stefani Seibold
2014-03-07  9:15   ` Fengguang Wu
2014-03-07  9:57     ` Stefani Seibold
2014-03-07 10:21       ` Fengguang Wu
2014-03-07 16:06         ` Stefani Seibold
2014-03-07 23:12           ` H. Peter Anvin
2014-03-07 10:36       ` Fengguang Wu
2014-03-07 23:44       ` Fengguang Wu
2014-03-09  8:08         ` Stefani Seibold
2014-03-10  0:00           ` H. Peter Anvin
2014-03-10 19:41             ` Greg Kroah-Hartman

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=531E4488.2000400@linux.intel.com \
    --to=hpa@linux.intel.com \
    --cc=Andreas.Brief@rohde-schwarz.com \
    --cc=Martin.Runge@rohde-schwarz.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=stefani@seibold.net \
    --cc=torvalds@linux-foundation.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 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.