[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jJMBDd3-Yab78aYwQ1N6VG7=BjARoTF1pDygPhaWA9VNQ@mail.gmail.com>
Date: Fri, 13 Jul 2018 21:44:15 -0700
From: Kees Cook <keescook@...omium.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: "Eric W. Biederman" <ebiederm@...ssion.com>,
Adrian Reber <adrian@...as.de>,
LKML <linux-kernel@...r.kernel.org>,
Oleg Nesterov <oleg@...hat.com>,
Pavel Emelyanov <xemul@...tuozzo.com>,
Andrei Vagin <avagin@...tuozzo.com>,
Hendrik Brueckner <brueckner@...ux.vnet.ibm.com>,
Cyrill Gorcunov <gorcunov@...nvz.org>,
Linux Containers <containers@...ts.linux-foundation.org>,
Josh Triplett <josh@...htriplett.org>
Subject: Re: [PATCH] kconfig: remove EXPERT from CHECKPOINT_RESTORE
On Fri, Jul 13, 2018 at 1:55 PM, Andrew Morton
<akpm@...ux-foundation.org> wrote:
> On Thu, 12 Jul 2018 11:33:33 -0500 ebiederm@...ssion.com (Eric W. Biederman) wrote:
>> What is the value of disabling this functionality ever?
>>
>> Is there any reason why we don't just delete CONFIG_CHECKPOINT_RESTORE
>> entirely?
>
> For the vast number of Linux machines which aren't servers? Check out
> some defconfigs - only one of arm's 119 defconfigs selects it.
Right, and I would bet the minification folks would like to keep it
out of their builds too. I think we should keep the config.
-Kees
--
Kees Cook
Pixel Security
Powered by blists - more mailing lists