Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Date:   Thu, 30 Jun 2022 15:11:58 +0200
From:   Michael Walle <michael@walle.cc>
To:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Rob Herring <robh@kernel.org>
Cc:     linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
        Guillaume Tucker <guillaume.tucker@collabora.com>
Subject: Regression for duplicate (?) console parameters on next-20220630
User-Agent: Roundcube Webmail/1.4.13
Message-ID: <8460ecf2a963c85793cf325e16725044@walle.cc>
Precedence: bulk

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