Linux kernel staging patches
 help / color / mirror / Atom feed
From: Marc Dietrich <marvin24@gmx.de>
To: Igor Putko <igorpetindev@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	ac100@lists.launchpad.net,  linux-tegra@vger.kernel.org,
	linux-staging@lists.linux.dev,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: nvec: nvec_power: use GFP_KERNEL in probe()
Date: Sun, 12 Jul 2026 17:41:45 +0200 (CEST)	[thread overview]
Message-ID: <1aad35a4-e5b9-c352-50ca-6dfa29ba3707@gmx.de> (raw)
In-Reply-To: <20260710150113.3041-1-igorpetindev@gmail.com>

Hello Igore,

On Fri, 10 Jul 2026, Igor Putko wrote:

> nvec_power_probe() calls devm_kzalloc() with GFP_NOWAIT, which
> disables direct reclaim and is meant for atomic context. probe()
> runs in normal process context and may sleep, so this needlessly
> risks a spurious -ENOMEM under memory pressure instead of just
> waiting for reclaim like every other probe() allocation does.
>
> nvec.c's own tegra_nvec_probe() already uses GFP_KERNEL for the
> identical pattern, confirming this is an oversight, not intentional.

I also see not reason to use GFP_NOWAIT here, even if it is unlikely to 
cause problems in this code path, as it is used during bootup where there 
should be "plenty" of RAM available. But I think it is a cleaner solution 
to do memory allocations. So
Acked-by: Marc Dietrich <marvin24@gmx.de>

> Signed-off-by: Igor Putko <igorpetindev@gmail.com>
> ---
> drivers/staging/nvec/nvec_power.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/nvec/nvec_power.c b/drivers/staging/nvec/nvec_power.c
> index 2faab9fde..c514d51a9 100644
> --- a/drivers/staging/nvec/nvec_power.c
> +++ b/drivers/staging/nvec/nvec_power.c
> @@ -377,7 +377,7 @@ static int nvec_power_probe(struct platform_device *pdev)
> 	struct nvec_chip *nvec = dev_get_drvdata(pdev->dev.parent);
> 	struct power_supply_config psy_cfg = {};
>
> -	power = devm_kzalloc(&pdev->dev, sizeof(struct nvec_power), GFP_NOWAIT);
> +	power = devm_kzalloc(&pdev->dev, sizeof(struct nvec_power), GFP_KERNEL);
> 	if (!power)
> 		return -ENOMEM;
>
> -- 
> 2.47.3
>
>

      reply	other threads:[~2026-07-12 15:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-10 15:01 [PATCH] staging: nvec: nvec_power: use GFP_KERNEL in probe() Igor Putko
2026-07-12 15:41 ` Marc Dietrich [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=1aad35a4-e5b9-c352-50ca-6dfa29ba3707@gmx.de \
    --to=marvin24@gmx.de \
    --cc=ac100@lists.launchpad.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=igorpetindev@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=linux-tegra@vger.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