From: ed@abdsec.com
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dan Rosenberg <dan.j.rosenberg@gmail.com>,
Dave Jones <davej@redhat.com>, Kees Cook <keescook@chromium.org>,
Kernel Hardening <kernel-hardening@lists.openwall.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] KERNEL: resource: Fix bug on leakage in /proc/iomem file
Date: Wed, 06 Apr 2016 13:05:56 -0500 [thread overview]
Message-ID: <5e5e7c7ced7bede343530ed1447d7453@abdsec.com> (raw)
In-Reply-To: <CA+55aFykp_ifLG=GkdGEM2keZs1Kb=eYcjjLz1LQh78LVSZong@mail.gmail.com>
First, I wrote your attached patch, but then I thought zeroing other
/proc/iomem values would be better. So I changed it.
Most distros don't use KASLR, but they use kptr_restrict. Without KASLR,
kptr_restirct most likely useless. As you said these things should be
done long ago
Emrah Demir
next prev parent reply other threads:[~2016-04-06 18:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 13:03 [PATCH] KERNEL: resource: Fix bug on leakage in /proc/iomem file Emrah Demir
2016-04-06 15:20 ` Linus Torvalds
2016-04-06 17:54 ` Linus Torvalds
2016-04-06 18:05 ` ed [this message]
2016-04-06 18:21 ` Kees Cook
2016-04-06 18:31 ` Linus Torvalds
2016-04-06 18:37 ` Kees Cook
2016-04-06 18:43 ` Linus Torvalds
2016-04-06 18:53 ` [kernel-hardening] " Yves-Alexis Perez
2016-04-06 19:02 ` Linus Torvalds
2016-04-06 19:11 ` Yves-Alexis Perez
2016-04-06 19:19 ` Borislav Petkov
2016-04-06 20:49 ` Ingo Molnar
2016-04-06 19:23 ` Bjørn Mork
2016-04-06 18:52 ` Christian Kujau
2016-04-06 18:53 ` Kees Cook
2016-04-06 21:19 ` Linus Torvalds
2016-04-06 21:27 ` Kees Cook
2016-04-06 21:32 ` Linus Torvalds
2016-04-14 4:27 ` Kees Cook
2016-04-14 7:39 ` Emrah Demir
2016-04-06 18:03 ` 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=5e5e7c7ced7bede343530ed1447d7453@abdsec.com \
--to=ed@abdsec.com \
--cc=dan.j.rosenberg@gmail.com \
--cc=davej@redhat.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox