From: Tommi Rantala <tommi.t.rantala@nokia.com>
To: Laura Abbott <labbott@redhat.com>, Kees Cook <keescook@chromium.org>
Cc: Linux-MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Eric Biggers <ebiggers@google.com>,
Dave Jones <davej@codemonkey.org.uk>
Subject: Re: sudo x86info -a => kernel BUG at mm/usercopy.c:78!
Date: Fri, 31 Mar 2017 08:44:43 +0300 [thread overview]
Message-ID: <bc2fa666-cbfb-e78d-39f7-be7ab66bf34d@nokia.com> (raw)
In-Reply-To: <a0abf5c5-f2f1-04f4-d660-f8c70042b11b@redhat.com>
On 30.03.2017 20:44, Laura Abbott wrote:
> On 03/30/2017 10:37 AM, Kees Cook wrote:
>>
>> Reads out of /dev/mem should be restricted to non-RAM on Fedora, yes?
>>
>> Tommi, do your kernels have CONFIG_STRICT_DEVMEM=y ?
>>
>> -Kees
>>
>
> CONFIG_STRICT_DEVMEM should be on in all Fedora kernels.
Yes, the fedora kernels do have it enabled:
$ grep STRICT_DEVMEM /boot/config-4.9.14-200.fc25.x86_64
CONFIG_STRICT_DEVMEM=y
CONFIG_IO_STRICT_DEVMEM=y
But I do not have it in my own build:
$ grep STRICT_DEVMEM .config
# CONFIG_STRICT_DEVMEM is not set
-Tommi
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Tommi Rantala <tommi.t.rantala@nokia.com>
To: Laura Abbott <labbott@redhat.com>, Kees Cook <keescook@chromium.org>
Cc: Linux-MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Eric Biggers <ebiggers@google.com>,
Dave Jones <davej@codemonkey.org.uk>
Subject: Re: sudo x86info -a => kernel BUG at mm/usercopy.c:78!
Date: Fri, 31 Mar 2017 08:44:43 +0300 [thread overview]
Message-ID: <bc2fa666-cbfb-e78d-39f7-be7ab66bf34d@nokia.com> (raw)
In-Reply-To: <a0abf5c5-f2f1-04f4-d660-f8c70042b11b@redhat.com>
On 30.03.2017 20:44, Laura Abbott wrote:
> On 03/30/2017 10:37 AM, Kees Cook wrote:
>>
>> Reads out of /dev/mem should be restricted to non-RAM on Fedora, yes?
>>
>> Tommi, do your kernels have CONFIG_STRICT_DEVMEM=y ?
>>
>> -Kees
>>
>
> CONFIG_STRICT_DEVMEM should be on in all Fedora kernels.
Yes, the fedora kernels do have it enabled:
$ grep STRICT_DEVMEM /boot/config-4.9.14-200.fc25.x86_64
CONFIG_STRICT_DEVMEM=y
CONFIG_IO_STRICT_DEVMEM=y
But I do not have it in my own build:
$ grep STRICT_DEVMEM .config
# CONFIG_STRICT_DEVMEM is not set
-Tommi
next prev parent reply other threads:[~2017-03-31 5:44 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 6:44 sudo x86info -a => kernel BUG at mm/usercopy.c:78! Tommi Rantala
2017-03-30 6:44 ` Tommi Rantala
2017-03-30 16:45 ` Kees Cook
2017-03-30 16:45 ` Kees Cook
2017-03-30 17:20 ` Mark Rutland
2017-03-30 17:20 ` Mark Rutland
2017-03-30 17:27 ` Laura Abbott
2017-03-30 17:27 ` Laura Abbott
2017-03-30 17:37 ` Kees Cook
2017-03-30 17:37 ` Kees Cook
2017-03-30 17:44 ` Laura Abbott
2017-03-30 17:44 ` Laura Abbott
2017-03-31 5:44 ` Tommi Rantala [this message]
2017-03-31 5:44 ` Tommi Rantala
2017-03-30 19:41 ` Dave Jones
2017-03-30 19:41 ` Dave Jones
2017-03-30 19:52 ` Kees Cook
2017-03-30 19:52 ` Kees Cook
2017-03-30 20:01 ` Dave Jones
2017-03-30 20:01 ` Dave Jones
2017-03-31 5:40 ` Tommi Rantala
2017-03-31 5:40 ` Tommi Rantala
2017-03-31 6:59 ` Tommi Rantala
2017-03-31 6:59 ` Tommi Rantala
2017-03-31 17:17 ` Dave Jones
2017-03-31 17:17 ` Dave Jones
2017-03-31 17:32 ` Kees Cook
2017-03-31 17:32 ` Kees Cook
2017-03-31 18:03 ` Dave Jones
2017-03-31 18:03 ` Dave Jones
2017-03-31 18:57 ` Andy Lutomirski
2017-03-31 18:57 ` Andy Lutomirski
2017-03-31 18:26 ` Linus Torvalds
2017-03-31 18:26 ` Linus Torvalds
2017-03-31 19:32 ` Tommi Rantala
2017-03-31 19:32 ` Tommi Rantala
2017-04-04 22:37 ` Kees Cook
2017-04-04 22:37 ` Kees Cook
2017-04-04 22:55 ` Linus Torvalds
2017-04-04 22:55 ` Linus Torvalds
2017-04-04 22:59 ` Kees Cook
2017-04-04 22:59 ` Kees Cook
2017-04-05 0:22 ` Linus Torvalds
2017-04-05 0:22 ` Linus Torvalds
2017-04-05 19:39 ` Kees Cook
2017-04-05 19:39 ` Kees Cook
2017-03-31 23:58 ` Kees Cook
2017-03-31 23:58 ` Kees Cook
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=bc2fa666-cbfb-e78d-39f7-be7ab66bf34d@nokia.com \
--to=tommi.t.rantala@nokia.com \
--cc=davej@codemonkey.org.uk \
--cc=ebiggers@google.com \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=mingo@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 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.