From: Hans de Goede <hdegoede@redhat.com>
To: Philipp Stanner <pstanner@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Bjorn Helgaas <bhelgaas@google.com>,
Sam Ravnborg <sam@ravnborg.org>,
dakr@redhat.com
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-pci@vger.kernel.org,
stable@kernel.vger.org
Subject: Re: [PATCH v2 10/10] drm/vboxvideo: fix mapping leaks
Date: Mon, 29 Jan 2024 12:15:53 +0100 [thread overview]
Message-ID: <e21c0853-d10a-44b5-917a-3f3c08102b87@redhat.com> (raw)
In-Reply-To: <20240123094317.15958-11-pstanner@redhat.com>
Hi Philipp,
On 1/23/24 10:43, Philipp Stanner wrote:
> When the PCI devres API was introduced to this driver, it was wrongly
> assumed that initializing the device with pcim_enable_device() instead
> of pci_enable_device() will make all PCI functions managed.
>
> This is wrong and was caused by the quite confusing devres API for PCI
> in which some, but not all, functions become managed that way.
>
> The function pci_iomap_range() is never managed.
>
> Replace pci_iomap_range() with the actually managed function
> pcim_iomap_range().
>
> Additionally, add a call to pcim_request_region() to ensure exclusive
> access to BAR 0.
I'm a bit worried about this last change. There might be
issues where the pcim_request_region() fails due to
e.g. a conflict with the simplefb / simpledrm code.
There is a drm_aperture_remove_conflicting_pci_framebuffers()
call done before hw_init() gets called, but still this
has been known to cause issues in the past.
Can you split out the adding of the pcim_request_region()
into a separate patch and *not* mark that separate patch
for stable ?
Regards,
Hans
>
> CC: <stable@kernel.vger.org> # v5.10+
> Fixes: 8558de401b5f ("drm/vboxvideo: use managed pci functions")
> Signed-off-by: Philipp Stanner <pstanner@redhat.com>
> ---
> drivers/gpu/drm/vboxvideo/vbox_main.c | 24 +++++++++++++-----------
> 1 file changed, 13 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/gpu/drm/vboxvideo/vbox_main.c b/drivers/gpu/drm/vboxvideo/vbox_main.c
> index 42c2d8a99509..7f686a0190e6 100644
> --- a/drivers/gpu/drm/vboxvideo/vbox_main.c
> +++ b/drivers/gpu/drm/vboxvideo/vbox_main.c
> @@ -42,12 +42,11 @@ static int vbox_accel_init(struct vbox_private *vbox)
> /* Take a command buffer for each screen from the end of usable VRAM. */
> vbox->available_vram_size -= vbox->num_crtcs * VBVA_MIN_BUFFER_SIZE;
>
> - vbox->vbva_buffers = pci_iomap_range(pdev, 0,
> - vbox->available_vram_size,
> - vbox->num_crtcs *
> - VBVA_MIN_BUFFER_SIZE);
> - if (!vbox->vbva_buffers)
> - return -ENOMEM;
> + vbox->vbva_buffers = pcim_iomap_range(
> + pdev, 0, vbox->available_vram_size,
> + vbox->num_crtcs * VBVA_MIN_BUFFER_SIZE);
> + if (IS_ERR(vbox->vbva_buffers))
> + return PTR_ERR(vbox->vbva_buffers);
>
> for (i = 0; i < vbox->num_crtcs; ++i) {
> vbva_setup_buffer_context(&vbox->vbva_info[i],
> @@ -115,12 +114,15 @@ int vbox_hw_init(struct vbox_private *vbox)
>
> DRM_INFO("VRAM %08x\n", vbox->full_vram_size);
>
> + ret = pcim_request_region(pdev, 0, "vboxvideo");
> + if (ret)
> + return ret;
> +
> /* Map guest-heap at end of vram */
> - vbox->guest_heap =
> - pci_iomap_range(pdev, 0, GUEST_HEAP_OFFSET(vbox),
> - GUEST_HEAP_SIZE);
> - if (!vbox->guest_heap)
> - return -ENOMEM;
> + vbox->guest_heap = pcim_iomap_range(pdev, 0,
> + GUEST_HEAP_OFFSET(vbox), GUEST_HEAP_SIZE);
> + if (IS_ERR(vbox->guest_heap))
> + return PTR_ERR(vbox->guest_heap);
>
> /* Create guest-heap mem-pool use 2^4 = 16 byte chunks */
> vbox->guest_pool = devm_gen_pool_create(vbox->ddev.dev, 4, -1,
next prev parent reply other threads:[~2024-01-29 11:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 9:42 [PATCH v2 00/10] Make PCI's devres API more consistent Philipp Stanner
2024-01-23 9:42 ` [PATCH v2 01/10] PCI: add new set of devres functions Philipp Stanner
2024-01-23 9:42 ` [PATCH v2 02/10] PCI: deprecate iomap-table functions Philipp Stanner
2024-01-23 9:43 ` [PATCH v2 03/10] PCI: warn users about complicated devres nature Philipp Stanner
2024-01-23 9:43 ` [PATCH v2 04/10] PCI: make devres region requests consistent Philipp Stanner
2024-01-23 9:43 ` [PATCH v2 05/10] PCI: move dev-enabled status bit to struct pci_dev Philipp Stanner
2024-01-23 9:43 ` [PATCH v2 06/10] PCI: move pinned " Philipp Stanner
2024-01-23 9:43 ` [PATCH v2 07/10] PCI: give pcim_set_mwi() its own devres callback Philipp Stanner
2024-01-23 9:43 ` [PATCH v2 08/10] PCI: give pci(m)_intx " Philipp Stanner
2024-01-23 9:43 ` [PATCH v2 09/10] PCI: remove legacy pcim_release() Philipp Stanner
2024-01-23 9:43 ` [PATCH v2 10/10] drm/vboxvideo: fix mapping leaks Philipp Stanner
2024-01-29 11:15 ` Hans de Goede [this message]
2024-01-29 13:12 ` Philipp Stanner
2024-01-23 10:23 ` [PATCH v2 00/10] Make PCI's devres API more consistent Philipp Stanner
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=e21c0853-d10a-44b5-917a-3f3c08102b87@redhat.com \
--to=hdegoede@redhat.com \
--cc=airlied@gmail.com \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=dakr@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=pstanner@redhat.com \
--cc=sam@ravnborg.org \
--cc=stable@kernel.vger.org \
--cc=tzimmermann@suse.de \
/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®