In function do_fb_ioctl(), the "arg" is the type of unsigned long,
and in "case FBIOBLANK:" this argument is casted into an int before
passig to fb_blank(). In fb_blank(), the comparision
if (blank > FB_BLANK_POWERDOWN) would be bypass if the original
"arg" is a large number, which is possible because it comes from
the user input. Fix this by adding the check before the function
call.
Signed-off-by: Yizhuo Zhai <yzhai003(a)ucr.edu>
---
drivers/video/fbdev/core/fbmem.c | 5 +++++
1 …
[View More]file changed, 5 insertions(+)
diff --git a/drivers/video/fbdev/core/fbmem.c b/drivers/video/fbdev/core/fbmem.c
index 0fa7ede94fa6..d5dec24c4d16 100644
--- a/drivers/video/fbdev/core/fbmem.c
+++ b/drivers/video/fbdev/core/fbmem.c
@@ -1162,6 +1162,11 @@ static long do_fb_ioctl(struct fb_info *info, unsigned int cmd,
case FBIOBLANK:
console_lock();
lock_fb_info(info);
+ if (arg > FB_BLANK_POWERDOWN) {
+ unlock_fb_info(info);
+ console_unlock();
+ return -EINVAL;
+ }
ret = fb_blank(info, arg);
/* might again call into fb_blank */
fbcon_fb_blanked(info, arg);
--
2.25.1
[View Less]
Currently autoloading for SPI devices does not use the DT ID table, it uses
SPI modalises. Supporting OF modalises is going to be difficult if not
impractical, an attempt was made but has been reverted, so this series
adds SPI IDs where they aren't provided for a given modalias.
v2:
- Rebase onto v5.17-rc1.
Mark Brown (2):
drm/ili9486: Add SPI ID table
drm/st7735r: Add SPI ID table
drivers/gpu/drm/tiny/ili9486.c | 2 ++
drivers/gpu/drm/tiny/st7735r.c | 1 +
2 files changed, 3 …
[View More]insertions(+)
base-commit: e783362eb54cd99b2cac8b3a9aeac942e6f6ac07
--
2.30.2
[View Less]
Currently autoloading for SPI devices does not use the DT ID table, it uses
SPI modalises. Supporting OF modalises is going to be difficult if not
impractical, an attempt was made but has been reverted, so this series
adds SPI IDs where they aren't provided for a given modalias.
v2:
- Rebase onto v5.17-rc1.
Mark Brown (3):
drm/panel-ilitek-il9322: Add SPI ID table
drm/panel-novotek-nt39016: Add SPI ID table
drm/ili9486: Add SPI ID table
drivers/gpu/drm/panel/panel-ilitek-ili9322.c | …
[View More]14 ++++++++++++++
drivers/gpu/drm/panel/panel-novatek-nt39016.c | 8 ++++++++
drivers/gpu/drm/tiny/ili9486.c | 2 ++
3 files changed, 24 insertions(+)
base-commit: e783362eb54cd99b2cac8b3a9aeac942e6f6ac07
--
2.30.2
[View Less]
Hi Dave & Daniel,
Tvrtko is out today, so sending the -rc3 -fixes PR on behalf of him (picked
and CI tested by Tvtko).
Major items are fix for GitLab #4698 (Dell DA310 Type-C dock issue) and
engine busyness inconsitent value/timeout fixes when running with GuC.
Then two fixes for error paths and a smatch detected divide by zero
fix.
Regards, Joonas
***
drm-intel-fixes-2022-02-03:
Fix GitLab issue #4698: DP monitor through Type-C dock(Dell DA310) doesn't work.
Fixes for inconsistent …
[View More]engine busyness value and read timeout with GuC.
Fix to use ALLOW_FAIL for error capture buffer allocation. Don't use
interruptible lock on error path. Smatch fix to reject zero sized overlays.
The following changes since commit 26291c54e111ff6ba87a164d85d4a4e134b7315c:
Linux 5.17-rc2 (2022-01-30 15:37:07 +0200)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-fixes-2022-02-03
for you to fetch changes up to 7d73c602154df56802a9e75ac212505fc1e9a2b6:
drm/i915/pmu: Fix KMD and GuC race on accessing busyness (2022-02-01 08:59:25 +0000)
----------------------------------------------------------------
Fix GitLab issue #4698: DP monitor through Type-C dock(Dell DA310) doesn't work.
Fixes for inconsistent engine busyness value and read timeout with GuC.
Fix to use ALLOW_FAIL for error capture buffer allocation. Don't use
interruptible lock on error path. Smatch fix to reject zero sized overlays.
----------------------------------------------------------------
Dan Carpenter (1):
drm/i915/overlay: Prevent divide by zero bugs in scaling
Imre Deak (1):
drm/i915/adlp: Fix TypeC PHY-ready status readout
Matthew Brost (2):
drm/i915: Allocate intel_engine_coredump_alloc with ALLOW_FAIL
drm/i915: Lock timeline mutex directly in error path of eb_pin_timeline
Umesh Nerlige Ramappa (2):
drm/i915/pmu: Use PM timestamp instead of RING TIMESTAMP for reference
drm/i915/pmu: Fix KMD and GuC race on accessing busyness
drivers/gpu/drm/i915/display/intel_overlay.c | 3 +
drivers/gpu/drm/i915/display/intel_tc.c | 3 +-
drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 9 +-
drivers/gpu/drm/i915/gt/uc/intel_guc.h | 5 +
drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 114 ++++++++++++++++++----
drivers/gpu/drm/i915/i915_gpu_error.c | 2 +-
drivers/gpu/drm/i915/i915_reg.h | 3 +-
7 files changed, 117 insertions(+), 22 deletions(-)
[View Less]
It looks like this code was accidentally dropped at some point(in a
slightly different form), so add it back. The gist is that if we know
the allocation will be one single chunk, then we can just annotate the
BO with I915_BO_ALLOC_CONTIGUOUS, even if the user doesn't bother. In
the future this might prove to be potentially useful.
Signed-off-by: Matthew Auld <matthew.auld(a)intel.com>
Cc: Thomas Hellström <thomas.hellstrom(a)linux.intel.com>
---
drivers/gpu/drm/i915/gem/…
[View More]i915_gem_region.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/i915/gem/i915_gem_region.c b/drivers/gpu/drm/i915/gem/i915_gem_region.c
index a4350227e9ae..dd414a2bcb06 100644
--- a/drivers/gpu/drm/i915/gem/i915_gem_region.c
+++ b/drivers/gpu/drm/i915/gem/i915_gem_region.c
@@ -57,6 +57,9 @@ i915_gem_object_create_region(struct intel_memory_region *mem,
size = round_up(size, default_page_size);
+ if (default_page_size == size)
+ flags |= I915_BO_ALLOC_CONTIGUOUS;
+
GEM_BUG_ON(!size);
GEM_BUG_ON(!IS_ALIGNED(size, I915_GTT_MIN_ALIGNMENT));
--
2.34.1
[View Less]