public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yves-Alexis Perez <corsac@debian.org>
To: kernel-hardening@lists.openwall.com, Kees Cook <keescook@chromium.org>
Cc: 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 20:53:12 +0200	[thread overview]
Message-ID: <1459968792.2818.22.camel@debian.org> (raw)
In-Reply-To: <CA+55aFx5Naq0rt99KZRWMf2GtyDaW1N2dapvdks_LMwaCYR13g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]

On mer., 2016-04-06 at 11:43 -0700, Linus Torvalds wrote:
> Hibernation is really quite nasty when you have to have a fairly big
> special partition for it, and shrink your memory down. Writing things
> to disk was a whole lot more reasonable back in the days when laptops
> had 16MB of memory.

Actually you just have to have a swap partition, which people still set as
more or less the ram size, I think, so all in all it works (especially if
people hibernate without the ram completely used).
> 
> I really wonder how many people use it with a modern laptop and
> distro. I doubt it's much faster than just rebooting the whole system
> anyway, and there are lots of downsides.

I quite never hibernate on my laptop (it wouldn't work anyway since I boot wit
kaslr and have PAX_SANITIZE), but I use hibernation on desktops where suspend
to ram doesn't work because of radeon or nvidia graphic card (actually suspend
usually works, resume doesn't). If/when suspend to ram works fine, I think
hibernation is mostly useless.

Regards,
-- 
Yves-Alexis


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2016-04-06 18:53 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
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             ` Yves-Alexis Perez [this message]
2016-04-06 19:02               ` [kernel-hardening] " 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=1459968792.2818.22.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 \
    /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