Displaying 3 results from an estimated 3 matches for "lusarz".
Did you mean:
slusarz
2014 Oct 16
0
[Intel-gfx] v3.17, i915 vs nouveau: possible recursive locking detected
We need ww mutexes and need to rewrite i915 a bit fo fix this all. I.e.
known issue. As long as your userspace isn't nasty nothing bad will ever
happen though.
-Daniel
On Mon, Oct 13, 2014 at 08:40:33PM +0200, Marcin ?lusarz wrote:
> =============================================
> [ INFO: possible recursive locking detected ]
> 3.17.0 #50 Not tainted
> ---------------------------------------------
> Xorg/1170 is trying to acquire lock:
> (&dev->struct_mutex){+.+.+.}, at: [<ffffffffa010ae93&...
2014 Oct 13
2
v3.17, i915 vs nouveau: possible recursive locking detected
=============================================
[ INFO: possible recursive locking detected ]
3.17.0 #50 Not tainted
---------------------------------------------
Xorg/1170 is trying to acquire lock:
(&dev->struct_mutex){+.+.+.}, at: [<ffffffffa010ae93>] i915_gem_unmap_dma_buf+0x33/0xc0 [i915]
but task is already holding lock:
(&dev->struct_mutex){+.+.+.}, at:
2013 Mar 11
3
[PATCH V3] get_maintainer: use filename-only regex match for Tegra
...es (see commit eb90d08 "get_maintainer: allow keywords to
match filenames"), but without the disadvantage that "random" file
content, such as comments, will ever match the regex. Hence, revert most
of that commit.
Switch the Tegra entry from using K: to N:
Reported-by: Marcin Slusarz <marcin.slusarz at gmail.com>
Suggested-by: Joe Perches <joe at perches.com>
Signed-off-by: Stephen Warren <swarren at nvidia.com>
---
v2: Corrected typo in MAINTAINERS documentation
v3: Squash 3 patches into one.
---
MAINTAINERS | 14 ++++++++------
scripts/get_m...