Re: [PATCH v2 2/2] drm/amd: validate user GEM object size

2018-12-22 Thread kbuild test robot
/linux/commits/Yu-Zhao/drm-amd-validate-user-pitch-alignment/20181222-153630 config: i386-allmodconfig (attached as .config) compiler: gcc-7 (Debian 7.3.0-1) 7.3.0 reproduce: # save the attached .config to linux build tree make ARCH=i386 All warnings (new ones prefixed

Re: After Vega 56/64 GPU hang I unable reboot system

2018-12-22 Thread Mikhail Gavrilov
On Thu, 20 Dec 2018 at 21:20, StDenis, Tom wrote: > > Sorry I didn't mean to be dismissive. It's just not a bug in umr though. > > On Fedora I can access those files as root just fine: > > tom@fx8:~$ sudo bash > [sudo] password for tom: > root@fx8:/home/tom# cd /sys/kernel/debug/dri/0 >

[PATCH v3 2/2] drm/amd: validate user GEM object size

2018-12-22 Thread Yu Zhao
When creating frame buffer, userspace may request to attach to a previously allocated GEM object that is smaller than what GPU requires. Validation must be done to prevent out-of-bound DMA, which could not only corrupt memory but also reveal sensitive data. This fix is not done in a common code

[PATCH v3 1/2] drm/amd: validate user pitch alignment

2018-12-22 Thread Yu Zhao
Userspace may request pitch alignment that is not supported by GPU. Some requests 32, but GPU ignores it and uses default 64 when cpp is 4. If GEM object is allocated based on the smaller alignment, GPU DMA will go out of bound. For GPU that does frame buffer compression, DMA writing out of bound

Re: [PATCH v2 2/2] drm/amd: validate user GEM object size

2018-12-22 Thread kbuild test robot
/linux/commits/Yu-Zhao/drm-amd-validate-user-pitch-alignment/20181222-153630 config: i386-randconfig-h1-12231406 (attached as .config) compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4 reproduce: # save the attached .config to linux build tree make ARCH=i386 All warnings (new ones prefixed