linux-kernel - Re: [REGRESSION] linux-next panics when trying to mount root

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <6a51ff05-89ed-cd57-6d90-3af51c7ce619@axentia.se>
Date:   Tue, 16 Jan 2018 16:02:35 +0100
From:   Peter Rosin <peda@...ntia.se>
To:     Boris Brezillon <boris.brezillon@...e-electrons.com>
Cc:     Richard Weinberger <richard@....at>,
        Rafał Miłecki <rafal@...ecki.pl>,
        Brian Norris <computersforpeace@...il.com>,
        David Woodhouse <dwmw2@...radead.org>,
        Marek Vasut <marek.vasut@...il.com>,
        Cyrille Pitchen <cyrille.pitchen@...ev4u.fr>,
        linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [REGRESSION] linux-next panics when trying to mount root

On 2018-01-16 15:21, Boris Brezillon wrote:
> On Tue, 16 Jan 2018 14:56:52 +0100
> Peter Rosin <peda@...ntia.se> wrote:
> 
>> Hmmm, I guess the question is if the command line should override the
>> device tree or not?
> 
> Yep, that's the problem. Now the core parses the compatible to decides
> which part parser should be used. The thing is, the "cmdline" parser is
> not yet exposing a compatible id, and even if it was, this would
> require patching all DTs to add this new compatible.
> 
> 	partitions {
> 		compatible = "cmdline", "fixed-partitions";
> 		...
> 	};
> 
> Not really an option, so I'll drop the 2 patches for now until we find a
> better solution.
> 
>> I'm going to send a patch for the above dts change either way...
> 
> If you want, but that does not solve the problem: we should not break
> existing users.

Well, don't let these devices stop you, they will not get a new kernel
w/o also getting a new dtb, and I can handle this just fine. But maybe
I'm just the first reporter and you'd rather not risk anything? Anyway,
just wanted to let you know where I stand...

Cheers,
Peter