From: Philipp Zabel <p.zabel@pengutronix.de>
To: Lucas Stach <l.stach@pengutronix.de>, etnaviv@lists.freedesktop.org
Cc: Russell King <linux+etnaviv@armlinux.org.uk>,
dri-devel@lists.freedesktop.org, kernel@pengutronix.de,
patchwork-lst@pengutronix.de
Subject: Re: [PATCH 1/4] drm/etnaviv: check for reaped mapping in etnaviv_iommu_unmap_gem
Date: Thu, 24 Mar 2022 16:39:22 +0100 [thread overview]
Message-ID: <842e036fec394bcc8f2d9859bc9e36c672556451.camel@pengutronix.de> (raw)
In-Reply-To: <20220323160825.3858619-1-l.stach@pengutronix.de>
On Mi, 2022-03-23 at 17:08 +0100, Lucas Stach wrote:
> When the mapping is already reaped the unmap must be a no-op, as we
> would otherwise try to remove the mapping twice, corrupting the
> involved
> data structures.
>
> Cc: stable@vger.kernel.org # 5.4
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de>
regards
Philipp
next prev parent reply other threads:[~2022-03-24 15:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 16:08 [PATCH 1/4] drm/etnaviv: check for reaped mapping in etnaviv_iommu_unmap_gem Lucas Stach
2022-03-23 16:08 ` [PATCH 2/4] drm/etnaviv: move MMU context ref/unref into map/unmap_gem Lucas Stach
2022-03-24 15:39 ` Philipp Zabel
2022-03-23 16:08 ` [PATCH 3/4] drm/etnaviv: move flush_seq increment into etnaviv_iommu_map/unmap Lucas Stach
2022-03-24 15:39 ` Philipp Zabel
2022-03-23 16:08 ` [PATCH 4/4] drm/etnaviv: reap idle softpin mappings when necessary Lucas Stach
2022-03-24 15:39 ` Philipp Zabel [this message]
2022-03-31 10:50 ` [PATCH 1/4] drm/etnaviv: check for reaped mapping in etnaviv_iommu_unmap_gem Guido Günther
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=842e036fec394bcc8f2d9859bc9e36c672556451.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.org \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux+etnaviv@armlinux.org.uk \
--cc=patchwork-lst@pengutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.