Re: [PATCH][Option 2] drm/vmwgfx: Fix an fb unlocking bug

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2016-02-25 at 19:23 +0000, Greg KH wrote:
> On Thu, Feb 25, 2016 at 10:27:02AM +0100, Thomas Hellstrom wrote:
> > A regression introduced when the master ttm lock was split into
> > two.
> > 
> > Reported-and-tested-by: Brian Paul <brianp@xxxxxxxxxx>
> > Signed-off-by: Thomas Hellstrom <thellstrom@xxxxxxxxxx>
> > Reviewed-by: Brian Paul <brianp@xxxxxxxxxx>
> > Cc: <stable@xxxxxxxxxxxxxxx> # 3.15.x - 4.2.x
> > ---
> > The stable commit "drm/ttm: Fixed a read/write lock imbalance"
> > exposes
> > this bug on kernels 3.15 through 4.2, causing a hang on vmwgfx
> > module
> > load. Please apply this commit if and only if
> > "drm/ttm: Fixed a read/write lock imbalance" has been applied.
> 
> What commit id was this one you are referring to?

025af18 drm/ttm: Fixed a read/write lock imbalance


So... Please apply this commit (i.e. please cherry-pick:

12617971 "drm/vmwgfx: Fix an fb unlocking bug"

) if and only if your stable tree 3.15 through 4.2 carries:

commit 025af189fb44250206dd8a32fa4a682392af3301
Author: Thomas Hellstrom <thellstrom@xxxxxxxxxx>
Date:   Fri Nov 20 11:43:50 2015 -0800

    drm/ttm: Fixed a read/write lock imbalance


--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]