Date:   Mon, 13 Feb 2023 08:16:06 +0100
From:   Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To:     Alexander Sverdlin <alexander.sverdlin@gmail.com>
Cc:     linux-kernel@vger.kernel.org,
        "Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH] driver: core: Prevent NULL pointer dereference in device
 name functions
Message-ID: <Y+njtiyDAEJolpZU@kroah.com>
References: <20230212220441.258258-1-alexander.sverdlin@gmail.com>
 <Y+nhnauiUDspXwNM@kroah.com>
 <78b980a9e913cb6d98fd7f99218ccb815926c9f3.camel@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <78b980a9e913cb6d98fd7f99218ccb815926c9f3.camel@gmail.com>
Precedence: bulk

On Mon, Feb 13, 2023 at 08:12:08AM +0100, Alexander Sverdlin wrote:
> Hi Greg,
> 
> On Mon, 2023-02-13 at 08:07 +0100, Greg Kroah-Hartman wrote:
> > > Prevent similar scenarios:
> > > 
> > > Unable to handle kernel NULL pointer dereference at virtual address 00000038
> > > ...
> > > PC is at dev_driver_string+0x0/0x38
> > 
> > How did this "scenario" happen?? What in-tree code caused this?
> > 
> 
> such in-tree code is not known to me, I stubled upon this putting dev_info()
> all over the code in the platform we currently convert to DT (cirrus ep93xx).

Instead of using dev_info() for tracing, use ftrace instead, that's what
it is there for!  :)

thanks,

greg k-h