From: Linus Torvalds <torvalds@linux-foundation.org>
To: Michal Hocko <mhocko@suse.com>
Cc: Alexander Potapenko <glider@google.com>,
Zhaoyang Huang <huangzhaoyang@gmail.com>,
Matthew Wilcox <willy@infradead.org>,
"zhaoyang.huang" <zhaoyang.huang@unisoc.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
ke.wang@unisoc.com, Marco Elver <elver@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Kees Cook <keescook@chromium.org>,
Eric Biggers <ebiggers@kernel.org>,
Mateusz Guzik <mjguzik@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] mm: make __GFP_SKIP_ZERO visible to skip zero operation
Date: Mon, 4 Sep 2023 10:34:25 -0700 [thread overview]
Message-ID: <CAHk-=wh2s26=Hj03cJXBWELmgCY=z5=mhTTDNVVKDAbda8g7Xw@mail.gmail.com> (raw)
In-Reply-To: <ZPWNTiAxZZh/kzew@dhcp22.suse.cz>
On Mon, 4 Sept 2023 at 00:55, Michal Hocko <mhocko@suse.com> wrote:
>
> Sooner or later this will become an
> unreviewable mess so the value of init_on_alloc will become very
> dubious.
The value of init_on_alloc is *already* very dubious.
Exactly because people will turn it off, because it hurts performance
so much - and in pointless ways.
You do realize that distributions - well, at least Fedora - simply
don't turn INIT_ON_ALLOC_DEFAULT_ON on at all?
So the current state of init_on_alloc is that nobody sane uses it. You
have to think you're special to enable it, because it is *so* bad.
Security people need to realize that the primary point of computing is
NEVER EVER security. Security is entirely pointless without a usable
system.
Unless security people realize that they are always secondary, they
aren't security people, they are just random wankers.
And people who state this truism had better not get shamed for
standing up to stupidity.
Linus
next prev parent reply other threads:[~2023-09-04 17:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 10:52 [PATCH] mm: make __GFP_SKIP_ZERO visible to skip zero operation zhaoyang.huang
2023-08-31 12:16 ` Matthew Wilcox
2023-09-01 10:29 ` Zhaoyang Huang
2023-09-01 12:55 ` Alexander Potapenko
2023-09-01 18:32 ` Kees Cook
2023-09-04 7:54 ` Michal Hocko
2023-09-04 17:34 ` Linus Torvalds [this message]
2023-09-04 18:22 ` Eric Biggers
2023-09-05 2:25 ` Alistair Popple
2023-09-06 14:17 ` Alexander Potapenko
2023-09-04 7:31 ` Michal Hocko
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='CAHk-=wh2s26=Hj03cJXBWELmgCY=z5=mhTTDNVVKDAbda8g7Xw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=dvyukov@google.com \
--cc=ebiggers@kernel.org \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=huangzhaoyang@gmail.com \
--cc=ke.wang@unisoc.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mjguzik@gmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=zhaoyang.huang@unisoc.com \
/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.