From: John Meneghini <jmeneghi@redhat.com>
To: Nilesh Javali <njavali@marvell.com>,
martin.petersen@oracle.com, lduncan@suse.com, cleech@redhat.com
Cc: linux-scsi@vger.kernel.org,
GR-QLogic-Storage-Upstream@marvell.com,
gregkh@linuxfoundation.org, Hannes Reinecke <hare@suse.de>,
Jerry Snitselaar <jsnitsel@redhat.com>,
Ming Lei <ming.lei@redhat.com>, Ewan Milne <emilne@redhat.com>
Subject: Re: [PATCH v2 0/3] UIO_MEM_DMA_COHERENT for cnic/bnx2/bnx2x
Date: Wed, 3 Jan 2024 10:31:28 -0500 [thread overview]
Message-ID: <a905fe13-93eb-4359-834a-9e80f7cca2e0@redhat.com> (raw)
In-Reply-To: <20240103091137.27142-1-njavali@marvell.com>
Nilesh,
Please explain what has been done to test these patches on bnx2i. Was testing done with iommu enabled/disabled? Was testing
done on any/all platforms, or was only x86_64 tested?
Thanks,
/John
On 1/3/24 04:11, Nilesh Javali wrote:
> During bnx2i iSCSI testing we ran into page refcounting issues in the
> uio mmaps exported from cnic to the iscsiuio process, and bisected back
> to the removal of the __GFP_COMP flag from dma_alloc_coherent calls.
>
> In order to fix these drivers to be able to mmap dma coherent memory via
> a uio device, without resorting to hacks and working with an iommu
> enabled, introduce a new uio mmap type backed by dma_mmap_coherent.
>
> While converting the uio interface, I also noticed that not all of these
> allocations were PAGE_SIZE aligned. Particularly the bnx2/bnx2x status
> block mapping was much smaller than any architecture page size, and I
> was concerned that it could be unintentionally exposing kernel memory.
>
> v2:
> - expose only the dma_addr within uio and cnic.
> - Cleanup newly added unions comprising virtual_addr
> and struct device
>
> Chris Leech (3):
> uio: introduce UIO_MEM_DMA_COHERENT type
> cnic,bnx2,bnx2x: use UIO_MEM_DMA_COHERENT
> cnic,bnx2,bnx2x: page align uio mmap allocations
>
> drivers/net/ethernet/broadcom/bnx2.c | 2 +
> .../net/ethernet/broadcom/bnx2x/bnx2x_main.c | 10 +++--
> drivers/net/ethernet/broadcom/cnic.c | 26 ++++++++-----
> drivers/net/ethernet/broadcom/cnic.h | 1 +
> drivers/net/ethernet/broadcom/cnic_if.h | 1 +
> drivers/uio/uio.c | 38 +++++++++++++++++++
> include/linux/uio_driver.h | 2 +
> 7 files changed, 67 insertions(+), 13 deletions(-)
>
next prev parent reply other threads:[~2024-01-03 15:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 9:11 [PATCH v2 0/3] UIO_MEM_DMA_COHERENT for cnic/bnx2/bnx2x Nilesh Javali
2024-01-03 9:11 ` [PATCH v2 1/3] uio: introduce UIO_MEM_DMA_COHERENT type Nilesh Javali
2024-01-04 14:54 ` kernel test robot
2024-01-04 20:20 ` Chris Leech
2024-01-09 11:52 ` [EXT] " Nilesh Javali
2024-01-03 9:11 ` [PATCH v2 2/3] cnic,bnx2,bnx2x: use UIO_MEM_DMA_COHERENT Nilesh Javali
2024-01-05 5:14 ` kernel test robot
2024-01-03 9:11 ` [PATCH v2 3/3] cnic,bnx2,bnx2x: page align uio mmap allocations Nilesh Javali
2024-01-03 15:31 ` John Meneghini [this message]
2024-01-03 16:00 ` [EXT] Re: [PATCH v2 0/3] UIO_MEM_DMA_COHERENT for cnic/bnx2/bnx2x Nilesh Javali
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=a905fe13-93eb-4359-834a-9e80f7cca2e0@redhat.com \
--to=jmeneghi@redhat.com \
--cc=GR-QLogic-Storage-Upstream@marvell.com \
--cc=cleech@redhat.com \
--cc=emilne@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hare@suse.de \
--cc=jsnitsel@redhat.com \
--cc=lduncan@suse.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=njavali@marvell.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