[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Yy2HSKb4AtcF+em6@liuwe-devbox-debian-v2>
Date: Fri, 23 Sep 2022 10:15:36 +0000
From: Wei Liu <wei.liu@...nel.org>
To: Saurabh Sengar <ssengar@...ux.microsoft.com>
Cc: ssengar@...rosoft.com, drawat.floss@...il.com, airlied@...ux.ie,
daniel@...ll.ch, linux-hyperv@...r.kernel.org,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
mikelley@...rosoft.com, Wei Liu <wei.liu@...nel.org>
Subject: Re: [PATCH] drm/hyperv: Don't overwrite dirt_needed value set by host
On Mon, Sep 12, 2022 at 08:32:46AM -0700, Saurabh Sengar wrote:
> Existing code is causing a race condition where dirt_needed value is
> already set by the host and gets overwritten with default value. Remove
> this default setting of dirt_needed, to avoid overwriting the value
> received in the channel callback set by vmbus_open. Removing this
> setting also means the default value for dirt_needed is changed to false
> as it's allocated by kzalloc which is similar to legacy hyperv_fb driver.
>
> Signed-off-by: Saurabh Sengar <ssengar@...ux.microsoft.com>
Applied to hyperv-next. Thanks.
I ended up reconstructing the patch myself since the said driver
changed. It is only a one line change so that's fine. If the committed
patch is wrong, please let me know.
Powered by blists - more mailing lists