Dmitry Osipenko 0f563a4bf6 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>
2017-06-15 14:23:50 +02:00
..
2015-08-13 13:49:37 +02:00
2016-11-07 12:58:12 +01:00
2015-08-13 13:47:45 +02:00
2017-04-05 18:11:47 +02:00
2017-04-05 18:11:47 +02:00
2017-05-05 11:47:01 +10:00
2016-11-07 13:01:42 +01:00
2013-10-31 09:55:45 +01:00
2016-07-16 11:23:50 +10:00
2016-07-04 11:34:31 +02:00
2017-04-05 18:11:48 +02:00
2015-01-27 10:14:40 +01:00
2014-04-04 09:12:51 +02:00
2016-07-16 11:23:50 +10:00
2017-04-05 18:11:48 +02:00
2017-04-05 18:11:48 +02:00