public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Rosato <mjrosato@linux.ibm.com>
To: Niklas Schnelle <schnelle@linux.ibm.com>,
	joro@8bytes.org, will@kernel.org, robin.murphy@arm.com,
	gerald.schaefer@linux.ibm.com
Cc: hca@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com,
	svens@linux.ibm.com, borntraeger@linux.ibm.com,
	farman@linux.ibm.com, clegoate@redhat.com, jgg@nvidia.com,
	iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-s390@vger.kernel.org, Halil Pasic <pasic@linux.ibm.com>
Subject: Re: [PATCH v4 2/4] s390/pci: store DMA offset in bus_dma_region
Date: Wed, 12 Feb 2025 10:23:50 -0500	[thread overview]
Message-ID: <52a8f09c-4a59-4439-9738-58f040fed0a5@linux.ibm.com> (raw)
In-Reply-To: <8380fe8052c9b972a8350394cb6655f6a9683d29.camel@linux.ibm.com>


>> +static void pci_dma_range_setup(struct pci_dev *pdev)
>> +{
>> +	struct zpci_dev *zdev = to_zpci(pdev);
>> +	struct bus_dma_region *map;
>> +
>> +	map = kzalloc(sizeof(*map), GFP_KERNEL);
>> +	if (!map)
>> +		return;
>> +
>> +	map->cpu_start = 0;
>> +	map->dma_start = PAGE_ALIGN(zdev->start_dma);
>> +	map->size = max(PAGE_ALIGN_DOWN(zdev->end_dma + 1) - map->dma_start, 0);
> 
> Ugh, this is my fault as I suggested it, but this max() doesn't work
> here. The zdev->end_dma is unsigned and so is map->dma_start so if the
> former is smaller underflow will occur and the max() won't save us.
> It's largely a theoretical issue since zdev->end_dma + 1 should always
> be larger than zdev->start_dma, but now the max() looks like we thought
> of that, but then it doesn't work.
> 
> If we handle it maybe just go with:
> 
> aligned_end = PAGE_ALIGN_DOWN(zdev->end_dma + 1);
> if (aligned_end >= map->dma_start)
>      map->size = aligned_end - map->dma_start;
> else
>      map->size = 0;
> 


Given that it's not really something that's supposed to happen, would it make sense then to add a 

WARN_ON_ONCE(map->size == 0);

At the end of this?


  reply	other threads:[~2025-02-12 15:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-07 20:53 [PATCH v4 0/4] iommu/s390: add support for IOMMU passthrough Matthew Rosato
2025-02-07 20:53 ` [PATCH v4 1/4] s390/pci: check for relaxed translation capability Matthew Rosato
2025-02-07 20:53 ` [PATCH v4 2/4] s390/pci: store DMA offset in bus_dma_region Matthew Rosato
2025-02-07 22:04   ` Niklas Schnelle
2025-02-12 15:23     ` Matthew Rosato [this message]
2025-02-12 16:15       ` Niklas Schnelle
2025-02-07 20:53 ` [PATCH v4 3/4] iommu/s390: handle IOAT registration based on domain Matthew Rosato
2025-02-10 11:44   ` Niklas Schnelle
2025-02-07 20:53 ` [PATCH v4 4/4] iommu/s390: implement iommu passthrough via identity domain Matthew Rosato
2025-02-10 11:47   ` Niklas Schnelle

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=52a8f09c-4a59-4439-9738-58f040fed0a5@linux.ibm.com \
    --to=mjrosato@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=clegoate@redhat.com \
    --cc=farman@linux.ibm.com \
    --cc=gerald.schaefer@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pasic@linux.ibm.com \
    --cc=robin.murphy@arm.com \
    --cc=schnelle@linux.ibm.com \
    --cc=svens@linux.ibm.com \
    --cc=will@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