linux-kernel - Regression for duplicate (?) console parameters on next-20220630

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

Date:   Thu, 30 Jun 2022 15:11:58 +0200
From:   Michael Walle <michael@...le.cc>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Rob Herring <robh@...nel.org>
Cc:     linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org,
        Guillaume Tucker <guillaume.tucker@...labora.com>
Subject: Regression for duplicate (?) console parameters on next-20220630

Hi,

I'm not sure it these are the correct recipients, feel free to CC 
others.

Since next-20220630 (or maybe also since next-20220629) I'm getting the

[    3.707900] WARNING: CPU: 0 PID: 38 at fs/kernfs/dir.c:531 
kernfs_put.part.0+0x1a0/0x1d4
[    3.716313] kernfs_put: console/active: released with incorrect 
active_ref 0

on both arm and arm64 boards. See for example:
https://linux.kernelci.org/test/case/id/62bd840b330c4851eaa39c16/

I have the console set in the device tree as well as on the commandline.
Up until recently that wasn't a problem and I guess that should be a 
valid
configuration. That being said, the warn() will go away if I remove the
console= parameter on the commandline.

I haven't had time to do a bisect yet. That will probably my next step;
or maybe kernelci will already do that for me, Guillaume? Unless someone
has some more insights/ideas.

-michael