public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Ratiu <adrian.ratiu@collabora.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	kernel@collabora.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/1] Initialize debugfs/ksysfs earlier?
Date: Fri, 04 Jun 2021 19:06:58 +0300	[thread overview]
Message-ID: <87tumdwr4t.fsf@collabora.com> (raw)
In-Reply-To: <YLojEy3wjq2R8Zsa@kroah.com>

On Fri, 04 Jun 2021, Greg Kroah-Hartman 
<gregkh@linuxfoundation.org> wrote:
> On Thu, Jun 03, 2021 at 11:00:00PM +0300, Adrian Ratiu wrote: 
>> Hi and thank you for the quick response!   On Thu, 03 Jun 2021, 
>> Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote: 
>> > 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?  
>>  Actually no, it works without problems before commit 
>> 56348560d495 and also works if I revert that commit or move the 
>> debugfs_init() and its dependency ksysfs_init() before the 
>> driver core init. 
> 
> And the file shows up properly?  How can that be?  Is it ok to 
> create a file before the superblock is created in the system? 
> For some reason I thought these were just silently failing and 
> no one noticed.  Maybe we should revisit that commit... 

Yes the file shows up and works properly, but I do not know 
why. My tests run after the system boots to an interactive shell 
and by that time everything is initialized and working.

I thought maybe there were some specific corner-cases you wanted 
to guard against by adding that initialization -ENOENT check, but 
honestly since we're not adding a file earlier in the driver core 
anymore, I'd just leave it as is because the check makes sense in 
general.

Thanks again,
Adrian

>
> thanks,
>
> greg k-h

      reply	other threads:[~2021-06-04 16:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03 12:55 [RFC PATCH 0/1] Initialize debugfs/ksysfs earlier? Adrian Ratiu
2021-06-03 12:55 ` [RFC PATCH 1/1] drivers: base: Expose probe failures via debugfs Adrian Ratiu
2021-06-03 13:16   ` Greg Kroah-Hartman
2021-06-03 20:00     ` Adrian Ratiu
2021-06-04 12:58       ` Greg Kroah-Hartman
2021-06-03 13:13 ` [RFC PATCH 0/1] Initialize debugfs/ksysfs earlier? Greg Kroah-Hartman
2021-06-03 20:00   ` Adrian Ratiu
2021-06-04 12:56     ` Greg Kroah-Hartman
2021-06-04 16:06       ` Adrian Ratiu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tumdwr4t.fsf@collabora.com \
    --to=adrian.ratiu@collabora.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox