> It can be turned off during boot by using init_on_alloc=0 kernel
parameter. So any user who is affected by this performance issue can
mitigate that by disabling the hardening option, after considering its
possible consequences.
And one can find the root cause only by test and compare with other
init_on_alloc=1 as a default servers Ubuntu users as a security
hardening mechanism, preventing a class of security issues from being
exploitable. Disabling that in general would allow those unknown
vulnerabilities open to be exploited.
It can be turned off during boot by using init_on_alloc=0
Hi, Mr. Ahrens.
For now, I am not yet convinced about removing the init_on_alloc default
option. I would agree if anyone argues that a page recycling mechanism
defeats the purpose of the option anyway. But it would, at least, be
restricted to whatever uses such mechanisms. (I am familiar with
apport information
** Tags added: apport-collected bionic uec-images
** Description changed:
Apologies if this is not the right forum to raise this concern. If not
please point me to a better place to have this discussion.
The 5.3 linux kernel added a new feature which allows pages to
@matthew.ahrens you can paste that URL into any browser on any machine
and authorise it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862822
Title:
init_on_alloc=1 causes big performance
I installed apport and python3-launchpadlib, and ran the requested
command:
$ apport-collect 1862822
The authorization page:
(https://launchpad.net/+authorize-token?oauth_token=KJm30XZW6qPv9HDzn45k_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
