From: Yves-Alexis Perez <corsac@debian.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
Kees Cook <keescook@chromium.org>, Emrah Demir <ed@abdsec.com>,
Dan Rosenberg <dan.j.rosenberg@gmail.com>,
Dave Jones <davej@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [kernel-hardening] Re: [PATCH] KERNEL: resource: Fix bug on leakage in /proc/iomem file
Date: Wed, 06 Apr 2016 21:11:07 +0200 [thread overview]
Message-ID: <1459969867.2818.28.camel@debian.org> (raw)
In-Reply-To: <CA+55aFxM2gWkV26ppU5hLh=s541Qx5yecbRySxDGKa1VP7NG=g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 551 bytes --]
On mer., 2016-04-06 at 12:02 -0700, Linus Torvalds wrote:
> So yeah, maybe swap partitions are still more common than I thought.
> And I didn't even consider the possibility that people would hibernate
> a desktop like you do.
To be fair, it's *my* use case, because suspend won't work but I'm lazy and
don't like to reopen everything I was doing, but still have to shut the
machine down once in a while (or to save power). And *I* would gladly trade
hibernation for kaslr and PAX_SANITIZE on those desktops.
Regards,
--
Yves-Alexis
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-04-06 19:11 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 13:03 [kernel-hardening] [PATCH] KERNEL: resource: Fix bug on leakage in /proc/iomem file Emrah Demir
2016-04-06 13:03 ` Emrah Demir
2016-04-06 15:20 ` [kernel-hardening] " Linus Torvalds
2016-04-06 15:20 ` Linus Torvalds
2016-04-06 17:54 ` [kernel-hardening] " Linus Torvalds
2016-04-06 17:54 ` Linus Torvalds
2016-04-06 18:05 ` [kernel-hardening] " ed
2016-04-06 18:05 ` ed
2016-04-06 18:21 ` [kernel-hardening] " Kees Cook
2016-04-06 18:21 ` Kees Cook
2016-04-06 18:31 ` [kernel-hardening] " Linus Torvalds
2016-04-06 18:31 ` Linus Torvalds
2016-04-06 18:37 ` [kernel-hardening] " Kees Cook
2016-04-06 18:37 ` Kees Cook
2016-04-06 18:43 ` [kernel-hardening] " Linus Torvalds
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 [this message]
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 19:23 ` Bjørn Mork
2016-04-06 18:52 ` [kernel-hardening] " Christian Kujau
2016-04-06 18:52 ` Christian Kujau
2016-04-06 18:53 ` [kernel-hardening] " Kees Cook
2016-04-06 18:53 ` Kees Cook
2016-04-06 21:19 ` [kernel-hardening] " Linus Torvalds
2016-04-06 21:19 ` Linus Torvalds
2016-04-06 21:27 ` [kernel-hardening] " Kees Cook
2016-04-06 21:27 ` Kees Cook
2016-04-06 21:32 ` [kernel-hardening] " Linus Torvalds
2016-04-06 21:32 ` Linus Torvalds
2016-04-14 4:27 ` [kernel-hardening] " Kees Cook
2016-04-14 4:27 ` Kees Cook
2016-04-14 7:39 ` [kernel-hardening] " Emrah Demir
2016-04-14 7:39 ` Emrah Demir
2016-04-06 18:03 ` [kernel-hardening] " Kees Cook
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=1459969867.2818.28.camel@debian.org \
--to=corsac@debian.org \
--cc=dan.j.rosenberg@gmail.com \
--cc=davej@redhat.com \
--cc=ed@abdsec.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 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.