From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Stefani Seibold <stefani@seibold.net>,
Fengguang Wu <fengguang.wu@intel.com>
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [x86, vdso] BUG: unable to handle kernel paging request at d34bd000
Date: Sun, 09 Mar 2014 17:00:31 -0700 [thread overview]
Message-ID: <531D009F.1060803@linux.intel.com> (raw)
In-Reply-To: <1394352497.1002.4.camel@wall-e.seibold.net>
On 03/09/2014 12:08 AM, Stefani Seibold wrote:
>
> This was not addressed to you, it was addressed to the x86 intel kernel
> developers to do more testing, since this piece of code has so many side
> effects. I apologizes this miss understanding.
>
I think you're misunderstanding.
We cannot debug every single contributors' code for them. There isn't
enough of us to go around. We have in fact stretched well beyond the
point which we usually can accommodate for this particular patchset.
-hpa
next prev parent reply other threads:[~2014-03-10 0:00 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
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 [this message]
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=531D009F.1060803@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefani@seibold.net \
/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