lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 31 Jul 2015 19:11:10 +0100
From:	Bryan O'Donoghue <pure.logic@...us-software.ie>
To:	Ilia Mirkin <imirkin@...m.mit.edu>
CC:	Peter Hurley <peter@...leysoftware.com>,
	Timo Aaltonen <tjaalton@...ian.org>,
	Emil Velikov <emil.l.velikov@...il.com>,
	Maarten Lankhorst <maarten.lankhorst@...onical.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
	Ben Skeggs <bskeggs@...hat.com>
Subject: Re: [PATCH] drm/nouveau/gem: tolerate a buffer specified multiple
 times

On 31/07/15 17:43, Bryan O'Donoghue wrote:
> On 31/07/15 17:36, Ilia Mirkin wrote:
>> Do you have a reproducible way of achieving the multiple buffer on
>> validation list thing?

Reliable enough. Start Chrome, then get Chrome to open a menu on top of 
it's own screen - for example click the top right menu bar - the thing 
with the three horizontal bars, scroll down to 'recent tabs' and let the 
mouse hover.

You'll get a menu that opens up over the main chrome screen and at that 
point you'll also get a 'multiple instances of buffer'

Basically drawing one window on top of another inside of the same Chrome 
tab.

I guess the same PID is mapping the same piece of memory twice because 
if I open a seperate Chrome window (which will have a seperate PID) and 
drag one window over the other we don't see a repeat.

If it helps

deckard@...eko:~$ dmesg | tail -n 5
[ 6900.249427] nouveau E[chrome[3176]] multiple instances of buffer 456 
on validation list
[ 6920.992475] nouveau E[chrome[3176]] multiple instances of buffer 458 
on validation list
[ 6934.277352] nouveau E[chrome[3176]] multiple instances of buffer 458 
on validation list
[ 6994.303600] nouveau E[chrome[3176]] multiple instances of buffer 458 
on validation list
[ 7067.436049] nouveau E[chrome[3176]] multiple instances of buffer 456 
on validation list


deckard@...eko:~$ ps -ax | grep chrome | grep 3176
  3176 pts/6    Sl+    0:29 /opt/google/chrome/chrome --type=gpu-process 
--channel=3143.0.1295591 ives-passed-by-fd --v8-snapshot-passed-by-fd 
--supports-dual-gpus=false --gpu-driver-bug-workarounds=2,29,32,45,55,57 
--disable-accelerated-video-decode --gpu-vendor-id=0x10de 
--gpu-device-id=0x0fe9 --gpu-driver-vendor --gpu-driver-version 
--v8-natives-passed-by-fd --v8-snapshot-passed-by-fd

> What GPU do you have? (Looking for a codename,
>> not a marketing name... lspci should have it... GFxxx or GKxxx or
>
> 01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT
> 750M Mac Edition] (rev a1) (prog-if 00 [VGA controller])
>      Subsystem: Apple Inc. Device 0130
>      Flags: bus master, fast devsel, latency 0, IRQ 45
>      Memory at c0000000 (32-bit, non-prefetchable) [size=16M]
>      Memory at 80000000 (64-bit, prefetchable) [size=256M]
>      Memory at 90000000 (64-bit, prefetchable) [size=32M]
>      I/O ports at 1000 [size=128]
>      Expansion ROM at c1000000 [disabled] [size=512K]
>      Capabilities: [60] Power Management version 3
>      Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
>      Capabilities: [78] Express Endpoint, MSI 00
>      Capabilities: [b4] Vendor Specific Information: Len=14 <?>
>      Capabilities: [100] Virtual Channel
>      Capabilities: [128] Power Budgeting <?>
>      Capabilities: [420] Advanced Error Reporting
>      Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1
> Len=024 <?>
>      Capabilities: [900] #19
>      Kernel driver in use: nouveau
>
> Macbook pro retina 2014

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ