From: "Jürgen Groß" <jgross@suse.com>
To: Oleksandr Andrushchenko <andr2000@gmail.com>,
xen-devel@lists.xenproject.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, boris.ostrovsky@oracle.com,
airlied@linux.ie, daniel@ffwll.ch
Cc: intel-gfx@lists.freedesktop.org, sstabellini@kernel.org,
dan.carpenter@oracle.com,
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: Re: [Intel-gfx] [PATCH 1/6] xen/gntdev: Fix dmabuf import with non-zero sgt offset
Date: Tue, 4 Aug 2020 08:11:47 +0200 [thread overview]
Message-ID: <acf507b8-462a-1fa0-c54f-cc5c44d3cc55@suse.com> (raw)
In-Reply-To: <20200731125109.18666-2-andr2000@gmail.com>
On 31.07.20 14:51, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
>
> It is possible that the scatter-gather table during dmabuf import has
> non-zero offset of the data, but user-space doesn't expect that.
> Fix this by failing the import, so user-space doesn't access wrong data.
>
> Fixes: 37ccb44d0b00 ("xen/gntdev: Implement dma-buf import functionality")
I can't find this commit in the tree. Did you mean bf8dc55b1358?
And don't you want to Cc stable for this patch, too?
>
> Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Acked-by: Juergen Gross <jgross@suse.com>
Juergen
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-08-04 6:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 12:51 [Intel-gfx] [PATCH 0/6] Fixes and improvements for Xen pvdrm Oleksandr Andrushchenko
2020-07-31 12:51 ` [Intel-gfx] [PATCH 1/6] xen/gntdev: Fix dmabuf import with non-zero sgt offset Oleksandr Andrushchenko
2020-08-04 6:11 ` Jürgen Groß [this message]
2020-08-04 6:34 ` Oleksandr Andrushchenko
2020-07-31 12:51 ` [Intel-gfx] [PATCH 2/6] drm/xen-front: Fix misused IS_ERR_OR_NULL checks Oleksandr Andrushchenko
2020-08-04 6:12 ` Jürgen Groß
2020-08-04 6:35 ` Oleksandr Andrushchenko
2020-08-04 6:39 ` Jürgen Groß
2020-08-06 9:20 ` Dan Carpenter
2020-08-06 9:17 ` Dan Carpenter
2020-07-31 12:51 ` [Intel-gfx] [PATCH 3/6] drm/xen-front: Add YUYV to supported formats Oleksandr Andrushchenko
2020-08-07 9:35 ` Noralf Trønnes
2020-07-31 12:51 ` [Intel-gfx] [PATCH 4/6] xen: Sync up with the canonical protocol definition in Xen Oleksandr Andrushchenko
2020-08-04 6:14 ` Jürgen Groß
2020-07-31 12:51 ` [Intel-gfx] [PATCH 5/6] drm/xen-front: Pass dumb buffer data offset to the backend Oleksandr Andrushchenko
2020-08-07 9:33 ` Noralf Trønnes
2020-07-31 12:51 ` [Intel-gfx] [PATCH 6/6] drm/xen-front: Add support for EDID based configuration Oleksandr Andrushchenko
2020-08-05 14:35 ` kernel test robot
2020-07-31 13:09 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fixes and improvements for Xen pvdrm Patchwork
2020-07-31 13:29 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-07-31 18:35 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=acf507b8-462a-1fa0-c54f-cc5c44d3cc55@suse.com \
--to=jgross@suse.com \
--cc=airlied@linux.ie \
--cc=andr2000@gmail.com \
--cc=boris.ostrovsky@oracle.com \
--cc=dan.carpenter@oracle.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr_andrushchenko@epam.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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