public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Petr Pavlu <petr.pavlu@suse.com>
To: Shyam Saini <shyamsaini@linux.microsoft.com>, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, linux-modules@vger.kernel.org,
	code@tyhicks.com, linux@rasmusvillemoes.dk,
	christophe.leroy@csgroup.eu, hch@infradead.org,
	mcgrof@kernel.org, frkaya@linux.microsoft.com,
	vijayb@linux.microsoft.com, linux@weissschuh.net,
	samitolvanen@google.com, da.gomez@samsung.com, rafael@kernel.org,
	dakr@kernel.org
Subject: Re: [PATCH v4 0/4] Properly handle module_kobject creation
Date: Wed, 5 Mar 2025 10:55:03 +0100	[thread overview]
Message-ID: <ae1f74bd-4e8c-4031-8175-240f5f8d7f17@suse.com> (raw)
In-Reply-To: <20250227184930.34163-1-shyamsaini@linux.microsoft.com>

On 2/27/25 19:49, Shyam Saini wrote:
> Hi Everyone,
> 
> This patch series fixes handling of module_kobject creation.
> A driver expect module_kset list populated with its corresponding
> module_kobject to create its /sys/module/<built-in-module>/drivers
> directory.
> 
> Since,
> [1] commit 96a1a2412acb ("kernel/params.c: defer most of param_sysfs_init() to late_initcall time")
> Call to populate module_kset list is deferred to save init time so that
> external watchdog doesn't fireup on some boards and Linux can take
> responsibility of feeding watchdog before it spuriously resets the
> system. However, [1] this fix caused another issue i.e, consumers
> of module_kset can't get related module_kobject during driver
> initialisation and hence can't create their
> /sys/module/<built-in-module>/drivers directory.
> 
> Consequently, [1] breaks user-space applications for eg: DPDK, which
> expects /sys/module/vfio_pci/drivers/pci:vfio-pci/new_id to be present.
> 
> The second issue was reported and the [2] revert of [1] was
> proposed. However, [2] the Revert doesn't address the original issue
> reported in [1].
> 
> This patch series addresses both issues reported in [1] and [2].
> 
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=96a1a2412acb
> [2] https://lore.kernel.org/lkml/20250130225803.321004-1-shyamsaini@linux.microsoft.com/

This looks ok to me. I only think the Fixes: tag should have remained
solely on the last patch in the series as that is the actual fix. I'll
adjust it when picking up the patches.

I'm going to wait for a few days if others still would like to comment
and then plan to queue this on modules-next.

@Greg, could I please get an Acked-by from you on the last patch in the
series as this affects the code in the driver core?

-- 
Thanks,
Petr

  parent reply	other threads:[~2025-03-05  9:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 18:49 [PATCH v4 0/4] Properly handle module_kobject creation Shyam Saini
2025-02-27 18:49 ` [PATCH v4 1/4] kernel: param: rename locate_module_kobject Shyam Saini
2025-02-27 18:49 ` [PATCH v4 2/4] kernel: refactor lookup_or_create_module_kobject() Shyam Saini
2025-02-27 18:49 ` [PATCH v4 3/4] kernel: globalize lookup_or_create_module_kobject() Shyam Saini
2025-02-27 18:49 ` [PATCH v4 4/4] drivers: base: handle module_kobject creation Shyam Saini
2025-04-15 15:29   ` Greg KH
2025-03-05  9:55 ` Petr Pavlu [this message]
2025-03-05 20:01   ` [PATCH v4 0/4] Properly " Shyam Saini
2025-03-18 16:23   ` Shyam Saini
2025-04-08 19:19   ` Shyam Saini
2025-04-08 19:21     ` Greg KH
2025-04-16 13:59 ` Petr Pavlu

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=ae1f74bd-4e8c-4031-8175-240f5f8d7f17@suse.com \
    --to=petr.pavlu@suse.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=code@tyhicks.com \
    --cc=da.gomez@samsung.com \
    --cc=dakr@kernel.org \
    --cc=frkaya@linux.microsoft.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=linux@weissschuh.net \
    --cc=mcgrof@kernel.org \
    --cc=rafael@kernel.org \
    --cc=samitolvanen@google.com \
    --cc=shyamsaini@linux.microsoft.com \
    --cc=vijayb@linux.microsoft.com \
    /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