This option does not (per its intent) present booting, it is just a check & warning.
There may be a bug with the check which is causing a failure to boot, but you are the first to report that aspect and that isn't what #852324 was about until now. Please use `reportbug kernel` to report a fresh bug describing your specific circumstances and your failure mode. Ian. On Wed, 2017-07-26 at 18:32 +0200, Helio Loureiro wrote: > Hi, > > VM doesn't boot with this parameter enabled, as confirmed by Linus > mail. So my upgraded to Stretch leaded to a complete system outage > because of this parameter. > > I held on kernel 3.19 from Jessie meanwhile. > > Best Regards, > Helio Loureiro > http://helio.loureiro.eng.br > https://se.linkedin.com/in/helioloureiro > http://twitter.com/helioloureiro > > > 2017-07-26 17:56 GMT+02:00 Ian Campbell <i...@debian.org>: > > On Wed, 2017-07-26 at 17:13 +0200, Helio Loureiro wrote: > > > Hi, > > > > > > As much it sounds correct to protect systems in this way, you > > broke > > > compatibility. I'm back to kernel 3.19 until this is fixed. > > > > > > So in order to have such parameter enabled, you should at the > > least > > > provide a bootparam option to toggle enabled or not. > > > > > > From my point of view as user, you should never break backward > > > compatibility, as bad is sounds in terms of security. And you > > should > > > never enforce it to users. > > > > Other than a single warning printed to dmesg during boot, what is > > actually broken for you? > > > > Ian. > > > >
