public inbox for kernel-hardening@lists.openwall.com
 help / color / mirror / Atom feed
From: "Bjørn Mork" <bjorn@mork.no>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kees Cook <keescook@chromium.org>,
	kernel-hardening@lists.openwall.com, 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: [kernel-hardening] Re: [PATCH] KERNEL: resource: Fix bug on leakage in /proc/iomem file
Date: Wed, 06 Apr 2016 21:23:00 +0200	[thread overview]
Message-ID: <87inzuv8x7.fsf@nemi.mork.no> (raw)
In-Reply-To: <CA+55aFx5Naq0rt99KZRWMf2GtyDaW1N2dapvdks_LMwaCYR13g@mail.gmail.com> (Linus Torvalds's message of "Wed, 6 Apr 2016 11:43:11 -0700")

Linus Torvalds <torvalds@linux-foundation.org> writes:

> I suspect there really aren't all that many hibernation users out
> there at all, and that yes, that would be the right default.
>
> 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.
>
> 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.

Huh? Do modern laptops now have infinite battery capacity?  I regularily
use hibernation as emergency shutdown when the battery runs out.  You
mean that never happens to other people?  Or you just take the hit and
stops everything you were currently doing, saving every open file etc?


Bjørn

  parent reply	other threads:[~2016-04-06 19:23 UTC|newest]

Thread overview: 22+ 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 15:20 ` [kernel-hardening] " 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
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 [this message]
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=87inzuv8x7.fsf@nemi.mork.no \
    --to=bjorn@mork.no \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox