From: Simon Horman <horms@kernel.org>
To: Thomas Fourier <fourier.thomas@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
Chas Williams <3chas3@gmail.com>,
"moderated list:ATM" <linux-atm-general@lists.sourceforge.net>,
"open list:ATM" <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] atm: idt77252: Add missing `dma_map_error()`
Date: Wed, 25 Jun 2025 10:40:13 +0100 [thread overview]
Message-ID: <20250625094013.GL1562@horms.kernel.org> (raw)
In-Reply-To: <4c6deafe-a6ec-40bf-873f-dc0df1a72dc4@gmail.com>
On Wed, Jun 25, 2025 at 11:14:56AM +0200, Thomas Fourier wrote:
> On 24/06/2025 18:51, Simon Horman wrote:
> > On Tue, Jun 24, 2025 at 08:41:47AM +0200, Thomas Fourier wrote:
> > > The DMA map functions can fail and should be tested for errors.
> > >
> > > Signed-off-by: Thomas Fourier <fourier.thomas@gmail.com>
> > > ---
> > > drivers/atm/idt77252.c | 5 +++++
> > > 1 file changed, 5 insertions(+)
> > >
> > > diff --git a/drivers/atm/idt77252.c b/drivers/atm/idt77252.c
> > > index 1206ab764ba9..f2e91b7d79f0 100644
> > > --- a/drivers/atm/idt77252.c
> > > +++ b/drivers/atm/idt77252.c
> > > @@ -852,6 +852,8 @@ queue_skb(struct idt77252_dev *card, struct vc_map *vc,
> > > IDT77252_PRV_PADDR(skb) = dma_map_single(&card->pcidev->dev, skb->data,
> > > skb->len, DMA_TO_DEVICE);
> > > + if (dma_mapping_error(&card->pcidev->dev, IDT77252_PRV_PADDR(skb)))
> > > + return -ENOMEM;
> > > error = -EINVAL;
> > > @@ -1857,6 +1859,8 @@ add_rx_skb(struct idt77252_dev *card, int queue,
> > > paddr = dma_map_single(&card->pcidev->dev, skb->data,
> > > skb_end_pointer(skb) - skb->data,
> > > DMA_FROM_DEVICE);
> > > + if (dma_mapping_error(&card->pcidev->dev, paddr))
> > > + goto outpoolrm;
> > > IDT77252_PRV_PADDR(skb) = paddr;
> > > if (push_rx_skb(card, skb, queue)) {
> > > @@ -1871,6 +1875,7 @@ add_rx_skb(struct idt77252_dev *card, int queue,
> > > dma_unmap_single(&card->pcidev->dev, IDT77252_PRV_PADDR(skb),
> > > skb_end_pointer(skb) - skb->data, DMA_FROM_DEVICE);
> > > +outpoolrm:
> > > handle = IDT77252_PRV_POOL(skb);
> > > card->sbpool[POOL_QUEUE(handle)].skb[POOL_INDEX(handle)] = NULL;
> > Hi Thomas,
> >
> > Can sb_pool_remove() be used here?
> > It seems to be the converse of sb_pool_add().
> > And safer than the code above.
> > But perhaps I'm missing something.
>
>
> Hi Simon,
>
> I don't see any reason why this would be a problem,
>
> though, I don't think it is related and the change should be in the same
> patch.
Yes, good point. In that case this patch looks good to me.
Reviewed-by: Simon Horman <horms@kernel.org>
> Should I create another patch for that?
I think that would be nice. But let's wait for this patch to land first.
next prev parent reply other threads:[~2025-06-25 9:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 6:41 [PATCH v2] atm: idt77252: Add missing `dma_map_error()` Thomas Fourier
2025-06-24 16:51 ` Simon Horman
2025-06-25 9:14 ` Thomas Fourier
2025-06-25 9:40 ` Simon Horman [this message]
2025-06-25 22:40 ` patchwork-bot+netdevbpf
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=20250625094013.GL1562@horms.kernel.org \
--to=horms@kernel.org \
--cc=3chas3@gmail.com \
--cc=fourier.thomas@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).