linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: Borislav Petkov <bp@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Kees Cook <keescook@chromium.org>,
	Laura Abbott <labbott@redhat.com>, Ingo Molnar <mingo@kernel.org>,
	Peter Anvin <hpa@zytor.com>,
	Fengguang Wu <fengguang.wu@intel.com>,
	Network Development <netdev@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>, LKP <lkp@01.org>,
	ast@fb.com, the arch/x86 maintainers <x86@kernel.org>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [net/bpf] 3051bf36c2 BUG: unable to handle kernel paging request at 0000a7cf
Date: Thu, 09 Mar 2017 23:11:17 +0100	[thread overview]
Message-ID: <58C1D305.8090802@iogearbox.net> (raw)
In-Reply-To: <20170309220732.ufqoqlawktsi2gao@pd.tnic>

On 03/09/2017 11:07 PM, Borislav Petkov wrote:
> On Thu, Mar 09, 2017 at 10:55:47PM +0100, Borislav Petkov wrote:
>> Can you make that:
>>
>> 	setup_clear_cpu_cap(X86_FEATURE_PGE);
>>
>> and see if it fixes your issue?
>
> Hmm, in reading the thread a bit more, that might not work. If I see it
> correctly, lguest does
>
>   clear_cpu_cap(&boot_cpu_data, X86_FEATURE_PGE);
>
> after the alternatives have run and static_cpu_has() sites have already
> been patched so clearing that bit won't bring anything.

Yeah, I just tried that out and it had no effect unfortunately, the
static_cpu_has() was still 1.

  reply	other threads:[~2017-03-09 22:14 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01 12:54 [net/bpf] 3051bf36c2 BUG: unable to handle kernel paging request at 0000a7cf Fengguang Wu
2017-03-02 20:23 ` Fengguang Wu
2017-03-02 20:40   ` Daniel Borkmann
2017-03-08 19:25     ` Linus Torvalds
2017-03-08 22:27       ` Daniel Borkmann
2017-03-08 22:36         ` Kees Cook
2017-03-08 22:51           ` Daniel Borkmann
2017-03-08 23:55           ` Laura Abbott
2017-03-09  5:36             ` Kees Cook
2017-03-09 13:04               ` Daniel Borkmann
2017-03-09 13:10                 ` Thomas Gleixner
2017-03-09 13:25                   ` Daniel Borkmann
2017-03-09 14:49                     ` Thomas Gleixner
2017-03-09 17:51                       ` Daniel Borkmann
2017-03-09 18:08                         ` David Miller
2017-03-09 18:10                         ` Linus Torvalds
2017-03-09 18:15                           ` Linus Torvalds
2017-03-09 18:31                             ` Daniel Borkmann
2017-03-09 21:32                               ` Daniel Borkmann
2017-03-09 21:55                                 ` Borislav Petkov
2017-03-09 22:07                                   ` Borislav Petkov
2017-03-09 22:11                                     ` Daniel Borkmann [this message]
2017-03-09 22:48                                       ` Borislav Petkov
2017-03-09 23:26                                         ` Linus Torvalds
2017-03-09 23:44                                           ` Borislav Petkov
2017-03-10  0:13                                             ` Daniel Borkmann
2017-03-12 21:40                                           ` Borislav Petkov
2017-03-09 14:53                     ` Daniel Borkmann
2017-03-09 17:48                       ` Linus Torvalds
2017-03-08 22:43         ` Linus Torvalds
2017-03-09  1:34           ` Fengguang Wu
2017-03-09 13:09       ` Thomas Gleixner

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=58C1D305.8090802@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=ast@fb.com \
    --cc=bp@suse.de \
    --cc=davem@davemloft.net \
    --cc=fengguang.wu@intel.com \
    --cc=hpa@zytor.com \
    --cc=keescook@chromium.org \
    --cc=labbott@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=mingo@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --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;
as well as URLs for NNTP newsgroup(s).