[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YLjVYaVfNGEkqPAQ@kroah.com>
Date: Thu, 3 Jun 2021 15:13:05 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Adrian Ratiu <adrian.ratiu@...labora.com>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
kernel@...labora.com, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/1] Initialize debugfs/ksysfs earlier?
On Thu, Jun 03, 2021 at 03:55:33PM +0300, Adrian Ratiu wrote:
> Hi Greg & all,
>
> I would like to add a new debugfs file like in the next patch but
> I'm having a problem with commit 56348560d495 ("debugfs: do not
> attempt to create a new file before the filesystem is initalized").
You should have had a problem before that commit happened as well,
right?
>
> The problem is debugfs is initialized after the driver core, during
> the core initcall, so I get an -ENOENT failure due to the above commit.
>
> My first reaction is to move the ksysfs_init() and debugfs_init() calls
> before the driver core init which works. Would that be ok?
>
> An alternative would be to create the new debugfs file somewhere else
> than the driver core, but I'm not sure where would be a good location,
> maybe in debugfs_init()? Doesn't seem right.
I don't really want the driver core to be messing with debugfs at all,
why is that needed? I'll respond on your patch...
thanks,
greg k-h
Powered by blists - more mailing lists