From: Damien Le Moal <dlemoal@kernel.org>
To: "Ionut Nechita (Wind River)" <ionut.nechita@windriver.com>,
"James E . J . Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: ahuang12@lenovo.com, axboe@kernel.dk,
damien.lemoal@opensource.wdc.com, hch@lst.de,
iommu@lists.linux.dev, ionut_n2001@yahoo.com,
john.g.garry@oracle.com, kbusch@kernel.org,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
linux-scsi@vger.kernel.org, m.szyprowski@samsung.com,
robin.murphy@arm.com, sagi@grimberg.me, stable@vger.kernel.org,
sunlightlinux@gmail.com
Subject: Re: [PATCH v3] scsi: sas: skip opt_sectors when DMA reports no real optimization hint
Date: Thu, 19 Mar 2026 12:27:27 +0900 [thread overview]
Message-ID: <1adabe3e-4497-4e71-b6a0-f3b81df322eb@kernel.org> (raw)
In-Reply-To: <20260318200532.51232-2-ionut.nechita@windriver.com>
On 3/19/26 05:05, Ionut Nechita (Wind River) wrote:
> +static unsigned int sas_dma_opt_sectors(struct device *dma_dev,
> + unsigned int max_sectors)
> +{
> + size_t opt = dma_opt_mapping_size(dma_dev);
> + unsigned int opt_sectors;
> +
> + if (opt >= dma_max_mapping_size(dma_dev))
> + return 0;
I really do not understand this one. How can the optimal DMA mapping size be
larger than the maximum possible DMA size ?
If that happens, it is a driver bug, we should WARN_ONCE and return
dma_max_mapping_size(), no ?
> +
> + opt = rounddown_pow_of_two(opt);
> + opt_sectors = opt >> SECTOR_SHIFT;
if opt is super large, can this overflow the 32-bits opt_sectors ?
> +
> + return min(opt_sectors, max_sectors);
> +}
> +
> static int sas_host_setup(struct transport_container *tc, struct device *dev,
> struct device *cdev)
> {
> @@ -239,10 +268,9 @@ static int sas_host_setup(struct transport_container *tc, struct device *dev,
> dev_printk(KERN_ERR, dev, "fail to a bsg device %d\n",
> shost->host_no);
>
> - if (dma_dev->dma_mask) {
> - shost->opt_sectors = min_t(unsigned int, shost->max_sectors,
> - dma_opt_mapping_size(dma_dev) >> SECTOR_SHIFT);
> - }
> + if (dma_dev->dma_mask)
> + shost->opt_sectors = sas_dma_opt_sectors(dma_dev,
> + shost->max_sectors);
Splitting the line after the "=" would make this look nicer:
if (dma_dev->dma_mask)
shost->opt_sectors =
sas_dma_opt_sectors(dma_dev, shost->max_sectors);
>
> return 0;
> }
--
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2026-03-19 3:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 20:05 [PATCH v3 0/1] scsi: sas: fix mkfs.xfs failure due to bogus optimal_io_size Ionut Nechita (Wind River)
2026-03-18 20:05 ` [PATCH v3] scsi: sas: skip opt_sectors when DMA reports no real optimization hint Ionut Nechita (Wind River)
2026-03-19 3:27 ` Damien Le Moal [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=1adabe3e-4497-4e71-b6a0-f3b81df322eb@kernel.org \
--to=dlemoal@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=ahuang12@lenovo.com \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@opensource.wdc.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=ionut.nechita@windriver.com \
--cc=ionut_n2001@yahoo.com \
--cc=john.g.garry@oracle.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=martin.petersen@oracle.com \
--cc=robin.murphy@arm.com \
--cc=sagi@grimberg.me \
--cc=stable@vger.kernel.org \
--cc=sunlightlinux@gmail.com \
/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