linux-kernel - Re: [PATCH v2] driver core: fw_devlink: Don't warn about sync

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAGETcx_=_wAdozOvF6KcNiJj4NeGzBy6sXYQsJMLZLFb819Lrw@mail.gmail.com>
Date: Tue, 7 Oct 2025 16:43:48 -0700
From: Saravana Kannan <saravanak@...gle.com>
To: Ulf Hansson <ulf.hansson@...aro.org>
Cc: "Rafael J . Wysocki" <rafael@...nel.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, 
	linux-pm@...r.kernel.org, Geert Uytterhoeven <geert@...ux-m68k.org>, 
	Nicolas Frattaroli <nicolas.frattaroli@...labora.com>, Heiko Stuebner <heiko@...ech.de>, 
	Sebastian Reichel <sebastian.reichel@...labora.com>, Sebin Francis <sebin.francis@...com>, 
	Diederik de Haas <didi.debian@...ow.org>, Tomi Valkeinen <tomi.valkeinen@...asonboard.com>, 
	Jon Hunter <jonathanh@...dia.com>, linux-arm-kernel@...ts.infradead.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] driver core: fw_devlink: Don't warn about sync_state() pending

On Tue, Oct 7, 2025 at 2:43 AM Ulf Hansson <ulf.hansson@...aro.org> wrote:
>
> Due to the wider deployment of the ->sync_state() support, for PM domains
> for example, we are receiving reports about the sync_state() pending
> message that is being logged in fw_devlink_dev_sync_state(). In particular
> as it's printed at the warning level, which is questionable.
>
> Even if it certainly is useful to know that the ->sync_state() condition
> could not be met, there may be nothing wrong with it. For example, a driver
> may be built as module and are still waiting to be initialized/probed. For
> this reason let's move to the info level for now.
>
> Reported-by: Geert Uytterhoeven <geert@...ux-m68k.org>
> Reported-by: Sebin Francis <sebin.francis@...com>
> Reported-by: Diederik de Haas <didi.debian@...ow.org>
> Reported-by: Jon Hunter <jonathanh@...dia.com>
> Reviewed-by: Tomi Valkeinen <tomi.valkeinen@...asonboard.com>
> Signed-off-by: Ulf Hansson <ulf.hansson@...aro.org>
> ---
>
> Changes in v2:
>         - Due to discussions on v1 and because the default Kconfig is to use the
>         FW_DEVLINK_SYNC_STATE_STRICT, I suggest that for now it may be best to
>         keep the warning level for the "Timed out.." print and only change the
>         "sync_state pending..." message.

Acked-by: Saravana Kannan <saravanak@...gle.com>

-Saravana

>
> ---
>  drivers/base/core.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/base/core.c b/drivers/base/core.c
> index d22d6b23e758..c62e428b95b0 100644
> --- a/drivers/base/core.c
> +++ b/drivers/base/core.c
> @@ -1784,7 +1784,7 @@ static int fw_devlink_dev_sync_state(struct device *dev, void *data)
>                 return 0;
>
>         if (fw_devlink_sync_state == FW_DEVLINK_SYNC_STATE_STRICT) {
> -               dev_warn(sup, "sync_state() pending due to %s\n",
> +               dev_info(sup, "sync_state() pending due to %s\n",
>                          dev_name(link->consumer));
>                 return 0;
>         }
> --
> 2.43.0
>