Since drm_property_create_range can be failed in memory pressure,
it needs to be checked and return -ENOMEM.
Signed-off-by: Insu Yun
---
drivers/gpu/drm/i2c/ch7006_drv.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/i2c/ch7006_drv.c b/drivers/gpu/drm/i2c/ch7006_drv.c
Since drm_property_create_range can be failed in memory pressure,
it needs to be handled.
Signed-off-by: Insu Yun
---
drivers/gpu/drm/gma500/framebuffer.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/gma500/framebuffer.c
b/drivers/gpu/drm/gma500/framebuffer.c
index
drm_property_create_range can be failed in memory pressure.
So, it needs to be handled.
Signed-off-by: Insu Yun
---
drivers/gpu/drm/nouveau/nouveau_display.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/gpu/drm/nouveau/nouveau_display.c
b/drivers/gpu/drm/nouveau
On Thu, Jan 28, 2016 at 7:08 PM, Ilia Mirkin wrote:
> On Thu, Jan 28, 2016 at 7:09 PM, Insu Yun wrote:
> > drm_property_create_range can be failed in memory pressure.
> > So, it needs to be handled.
> >
> > Signed-off-by: Insu Yun
> > ---
> > driver
On Fri, Jan 29, 2016 at 12:46 PM, One Thousand Gnomes <
gnomes at lxorguk.ukuu.org.uk> wrote:
> On Thu, 28 Jan 2016 19:05:16 -0500
> Insu Yun wrote:
>
> > Since drm_property_create_range can be failed in memory pressure,
> > it needs to be handled.
>
In drm_dp_mst_allocate_vcpi, it returns true in two paths,
but in one path, there is no reference couting decrease.
Signed-off-by: Insu Yun
---
drivers/gpu/drm/drm_dp_mst_topology.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/drm_dp_mst_topology.c
b/drivers/gpu/drm
Since kmalloc can be failed in memory pressure,
check and return error code
otherwise NULL deference could be happened
Signed-off-by: Insu Yun
---
drivers/gpu/drm/qxl/qxl_kms.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/qxl/qxl_kms.c b/drivers/gpu/drm/qxl/qxl_kms.c
For me, it is good :)
On Tue, Feb 9, 2016 at 9:48 AM, Harry Wentland
wrote:
> This looks good but we should probably do the same for all return paths
> when reference for port has been acquired.
>
> Please see attached patch.
>
> Thanks,
> Harry
>
>
> On 2016-
drm_property_create_range can be failed in memory pressure
Therefore, check return value and handle an error
Signed-off-by: Insu Yun
---
drivers/gpu/drm/drm_crtc.c | 30 ++
1 file changed, 30 insertions(+)
diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm
Since kmalloc can be failed in memory pressure,
when fails, return error code.
Signed-off-by: Insu Yun
---
drivers/gpu/drm/qxl/qxl_kms.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/qxl/qxl_kms.c b/drivers/gpu/drm/qxl/qxl_kms.c
index b2977a1..2e99854 100644
--- a
Signed-off-by: Insu Yun
---
drivers/gpu/drm/i915/intel_dsi_panel_vbt.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/i915/intel_dsi_panel_vbt.c
b/drivers/gpu/drm/i915/intel_dsi_panel_vbt.c
index a5e99ac..4e279dd 100644
--- a/drivers/gpu/drm/i915/intel_dsi_panel_vbt.c
Since devm_kzalloc can be failed, it needs to be checked
if not, NULL dereference could be happened.
Signed-off-by: Insu Yun
---
drivers/gpu/drm/i915/intel_dsi_panel_vbt.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/i915/intel_dsi_panel_vbt.c
b/drivers/gpu/drm/i915
On Wed, Dec 30, 2015 at 4:16 AM, Jani Nikula
wrote:
> On Tue, 29 Dec 2015, Insu Yun wrote:
> > Signed-off-by: Insu Yun
> > ---
> > drivers/gpu/drm/i915/intel_dsi_panel_vbt.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/drivers/gpu/drm
13 matches
Mail list logo
