diff options
author | Dmitry Osipenko <digetx@gmail.com> | 2017-06-15 02:18:37 +0300 |
---|---|---|
committer | Thierry Reding <treding@nvidia.com> | 2017-06-15 15:23:50 +0300 |
commit | 0f563a4bf66e5182f0882efee398f7e6bc0bb1be (patch) | |
tree | 3197816e7ddebd5d8360c6aae439d20a956b6a95 /include/linux/host1x.h | |
parent | ef81624994845a50e90c6a0ff57f17d1c96bff78 (diff) | |
download | linux-0f563a4bf66e5182f0882efee398f7e6bc0bb1be.tar.xz |
gpu: host1x: Forbid unrelated SETCLASS opcode in the firewall
Several channels could be made to write the same unit concurrently via
the SETCLASS opcode, trusting userspace is a bad idea. It should be
possible to drop the per-client channel reservation and add a per-unit
locking by inserting MLOCK's to the command stream to re-allow the
SETCLASS opcode, but it will be much more work. Let's forbid the
unit-unrelated class changes for now.
Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
Reviewed-by: Erik Faye-Lund <kusmabite@gmail.com>
Reviewed-by: Mikko Perttunen <mperttunen@nvidia.com>
Signed-off-by: Thierry Reding <treding@nvidia.com>
Diffstat (limited to 'include/linux/host1x.h')
-rw-r--r-- | include/linux/host1x.h | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/include/linux/host1x.h b/include/linux/host1x.h index ba0b245da732..b5358f855d9e 100644 --- a/include/linux/host1x.h +++ b/include/linux/host1x.h @@ -251,6 +251,9 @@ struct host1x_job { /* Check if register is marked as an address reg */ int (*is_addr_reg)(struct device *dev, u32 reg, u32 class); + /* Check if class belongs to the unit */ + int (*is_valid_class)(u32 class); + /* Request a SETCLASS to this class */ u32 class; |