DMA Engine development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>
Cc: Frank.Li@kernel.org, dmaengine@vger.kernel.org, vkoul@kernel.org
Subject: Re: [PATCH v2 6/7] gpib: fmh_gpib: Replace dma_request_slave_channel() by dma_request_chan()
Date: Fri, 18 Sep 2026 12:09:47 +0000	[thread overview]
Message-ID: <20260918120947.A38E71F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260918113727.1898998-7-andriy.shevchenko@linux.intel.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] gpib: leaking -EPROBE_DEFER to userspace via ioctl
--

commit ed7181f3c8edddd4643c5d2a68386dacb851bb22
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

gpib: fmh_gpib: Replace dma_request_slave_channel() by dma_request_chan()

This commit replaces the deprecated dma_request_slave_channel() with
dma_request_chan() in the fmh_gpib driver. It propagates the specific
error code returned by dma_request_chan() rather than returning a hardcoded
-EIO.

> diff --git a/drivers/gpib/fmh_gpib/fmh_gpib.c b/drivers/gpib/fmh_gpib/fmh_gpib.c
> index 5e10e9353fedd..4ab9b0a317fdb 100644
> --- a/drivers/gpib/fmh_gpib/fmh_gpib.c
> +++ b/drivers/gpib/fmh_gpib/fmh_gpib.c
> @@ -1458,11 +1458,15 @@ static int fmh_gpib_attach_impl(struct gpib_board *board, const struct gpib_boar
>  	e_priv->irq = irq;
>  
>  	if (acquire_dma) {
> -		e_priv->dma_channel = dma_request_slave_channel(board->dev, "rxtx");
> -		if (!e_priv->dma_channel) {
> +		struct dma_chan *tmp_chan;
> +
> +		tmp_chan = dma_request_chan(board->dev, "rxtx");
> +		retval = PTR_ERR_OR_ZERO(tmp_chan);
> +		if (retval) {
>  			dev_err(board->dev, "failed to acquire dma channel \"rxtx\".\n");
> -			return -EIO;
> +			return retval;

[Severity: Medium]
Could this leak -EPROBE_DEFER to userspace?

If dma_request_chan() fails due to an unavailable DMA controller, it returns
-EPROBE_DEFER. Because fmh_gpib_attach_impl() is called when a userspace
application configures the board via the IBONL ioctl:

ibioctl()
  online_ioctl()
    ibonline()
      attach()
        fmh_gpib_attach_impl()

This kernel-internal error code would be returned directly across the syscall
boundary.

Userspace applications expecting standard POSIX error codes like -EIO, -EAGAIN,
or -ENODEV might break when encountering -EPROBE_DEFER.

>  		}
> +		e_priv->dma_channel = tmp_chan;
>  	}

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260918113727.1898998-1-andriy.shevchenko@linux.intel.com?part=6

  reply	other threads:[~2026-09-18 12:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18 11:34 [PATCH v2 0/7] ASoC et alia: Convert to use dma_request_chan() Andy Shevchenko
2026-09-18 11:34 ` [PATCH v2 1/7] ASoC: stm32: spdifrx: Drop mention of the deprecated and unused call Andy Shevchenko
2026-09-18 11:34 ` [PATCH v2 2/7] ASoC: sprd: Replace dma_request_slave_channel() by dma_request_chan() Andy Shevchenko
2026-09-18 11:52   ` sashiko-bot
2026-09-18 11:34 ` [PATCH v2 3/7] ASoC: soc-generic-dmaengine-pcm: " Andy Shevchenko
2026-09-18 11:34 ` [PATCH v2 4/7] ASoC: pxa: " Andy Shevchenko
2026-09-18 11:34 ` [PATCH v2 5/7] ASoC: fsl_asrc: " Andy Shevchenko
2026-09-18 13:55   ` Frank Li
2026-09-18 11:34 ` [PATCH v2 6/7] gpib: fmh_gpib: " Andy Shevchenko
2026-09-18 12:09   ` sashiko-bot [this message]
2026-09-18 11:34 ` [PATCH v2 7/7] dmaengine: Remove deprecated dma_request_slave_channel() Andy Shevchenko
2026-09-18 17:58   ` Vinod Koul
2026-09-19 13:56     ` Andy Shevchenko
2026-09-21 12:01 ` [PATCH v2 0/7] ASoC et alia: Convert to use dma_request_chan() Mark Brown

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=20260918120947.A38E71F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=vkoul@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