linux-kernel - Re: Boot problem on PPC with 4.4-git

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAPcyv4gfZMca5J4eRc+OnJJPakgktBe2WWQ8cSfwt0agXTTQUQ@mail.gmail.com>
Date:	Wed, 20 Jan 2016 14:19:51 -0800
From:	Dan Williams <dan.j.williams@...el.com>
To:	Larry Finger <Larry.Finger@...inger.net>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Boot problem on PPC with 4.4-git - Bisected to commit 21266be

On Wed, Jan 20, 2016 at 1:36 PM, Larry Finger <Larry.Finger@...inger.net> wrote:
> On 01/20/2016 02:33 PM, Dan Williams wrote:
> That isn't quite right. I added that patch, and restored the 4.4.0
> configuration. That one has "CONFIG_STRICT_DEVM=y". After I ran "make
> oldconfig", CONFIG_STRICT_DEVM was still set, which kills rebooting.
>
> When I repeated the process, but removed the CONFIG_STRICT_DEVM line from
> .config before I ran "make oldconfig", then I got a bootable configuration.
> It seems that once STRICT_DEVM is yes, only a "make menuconfig", or
> equivalent, will let you turn it off.

This matches my expectation.  The fix stops defaulting it on when
CONFIG_STRICT_DEVM is set, but if you already have it set this change
will have no effect.  In other words if you take a old config from
before CONFIG_IO_STRICT_DEVMEM was introduced it won't get turned
on...