From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Valerii Sokolov <valerii.sokolov@pm.me>
Cc: Antti Laakso <antti.laakso@linux.intel.com>,
Sarang Sapre <sarang.sapre@intel.com>,
Divyamani Tripathi <divyamani.tripathi@intel.com>,
Manik Bajpai <manik.bajpai@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 08/11] media: intel/ipu6: return an error from ipu6_dma_map_sgtable() on failure
Date: Sat, 31 Oct 2026 00:45:34 +0200 [thread overview]
Message-ID: <auUeDraiy9tu1NDg@kekkonen.localdomain> (raw)
In-Reply-To: <20261023195446.22578-9-valerii.sokolov@pm.me>
Hi Valerii,
Thank you for the set. These are really nice fixes!
On Fri, Oct 23, 2026 at 07:55:58PM +0000, Valerii Sokolov wrote:
> ipu6_dma_map_sg() returns 0 when ipu6_mmu_map() fails, but
> ipu6_dma_map_sgtable() only treats negative values as errors. On failure
> it therefore sets sgt->nents to 0 and returns success, and callers such
> as ipu6_isys_buf_init() and ipu6_map_fw_region() go on to hand the
> hardware an address that is not mapped in the IPU MMU.
>
> Return -ENOMEM when ipu6_dma_map_sg() maps no entries.
>
> Fixes: daabc5c64703 ("media: ipu6: not override the dma_ops of device in driver")
> Cc: stable@vger.kernel.org
> Signed-off-by: Valerii Sokolov <valerii.sokolov@pm.me>
> ---
> drivers/media/pci/intel/ipu6/ipu6-dma.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/media/pci/intel/ipu6/ipu6-dma.c b/drivers/media/pci/intel/ipu6/ipu6-dma.c
> index a923a1e4bd..37b5c25259 100644
> --- a/drivers/media/pci/intel/ipu6/ipu6-dma.c
> +++ b/drivers/media/pci/intel/ipu6/ipu6-dma.c
> @@ -459,8 +459,8 @@ int ipu6_dma_map_sgtable(struct ipu6_bus_device *sys, struct sg_table *sgt,
> int nents;
>
> nents = ipu6_dma_map_sg(sys, sgt->sgl, sgt->nents, dir, attrs);
> - if (nents < 0)
> - return nents;
> + if (nents <= 0)
> + return nents < 0 ? nents : -ENOMEM;
I think this has been written as-is since the thinking has been a negative
error code is returned on error. So I'd fix this on ipu6_dma_map_sg() side
instead.
dma_map_sg() returns 0 on error (which is probably the source of this
discrepancy) but I don't think we need to align the error codes to that.
>
> sgt->nents = nents;
>
--
Kind regards,
Sakari Ailus
next prev parent reply other threads:[~2026-10-30 22:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 19:55 [PATCH v1 00/11] media: intel/ipu6: bounds, leak, and error handling fixes Valerii Sokolov
2026-10-23 19:55 ` [PATCH v1 01/11] media: intel/ipu6: move busy check to ipu6_isys_vidioc_s_fmt_vid_cap() Valerii Sokolov
2026-10-23 19:55 ` [PATCH v1 02/11] media: intel/ipu6: fix firmware message buffer leak on send failure Valerii Sokolov
2026-10-23 19:55 ` [PATCH v1 03/11] media: intel/ipu6: check pin bounds in ipu6_isys_fw_pin_cfg() Valerii Sokolov
2026-10-23 19:55 ` [PATCH v1 04/11] media: intel/ipu6: clamp crop top offset in ipu6_isys_csi2_set_sel() Valerii Sokolov
2026-10-23 19:55 ` [PATCH v1 05/11] media: intel/ipu6: check irq_status mask before calling subdevice ISR Valerii Sokolov
2026-10-23 19:55 ` [PATCH v1 06/11] media: intel/ipu6: clean up fwctx on ipu6_fw_com_open() failure Valerii Sokolov
2026-10-23 19:55 ` [PATCH v1 07/11] media: intel/ipu6: fix IOVA leak on first entry failure in ipu6_dma_map_sg() Valerii Sokolov
2026-10-23 19:55 ` [PATCH v1 08/11] media: intel/ipu6: return an error from ipu6_dma_map_sgtable() on failure Valerii Sokolov
2026-10-30 22:45 ` Sakari Ailus [this message]
2026-11-03 21:02 ` Valerii Sokolov
2026-10-23 19:56 ` [PATCH v1 09/11] media: intel/ipu6: unmap the dummy L2 page table in ipu6_mmu_destroy() Valerii Sokolov
2026-10-23 19:56 ` [PATCH v1 10/11] media: intel/ipu6: pass the device to dev_err() in ipu6_mmu_unmap() Valerii Sokolov
2026-10-23 19:56 ` [PATCH v1 11/11] media: intel/ipu6: fix EOF sequence logging in ipu6_isys_isr_one() Valerii Sokolov
2026-10-30 9:05 ` [PATCH v1 00/11] media: intel/ipu6: bounds, leak, and error handling fixes Antti Laakso
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=auUeDraiy9tu1NDg@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=antti.laakso@linux.intel.com \
--cc=divyamani.tripathi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=manik.bajpai@intel.com \
--cc=mchehab@kernel.org \
--cc=sarang.sapre@intel.com \
--cc=valerii.sokolov@pm.me \
/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
all inboxes | Powered by JetHome®