From: Helge Deller <deller@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: [GIT PULL] fbdev last fixes for v6.17-rc1
Date: Thu, 7 Aug 2025 13:21:47 +0200 [thread overview]
Message-ID: <aJSMS8PhMMe0NL63@p100> (raw)
Hi Linus,
please pull two more fbdev fixes for 6.17-rc1:
One patch reverts a previous stable tree patch which broke the VGA console,
the other fixes an out-of-bounds access bug which may happen during console
resizing when a console is mapped to a frame buffer.
Both patches are tagged for stable series.
Thanks,
Helge
----------------------------------------------------------------
The following changes since commit 038d61fd642278bab63ee8ef722c50d10ab01e8f:
Linux 6.16 (2025-07-27 14:26:38 -0700)
are available in the Git repository at:
http://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev.git tags/fbdev-for-6.17-rc1-2
for you to fetch changes up to e4fc307d8e24f122402907ebf585248cad52841d:
Revert "vgacon: Add check for vc_origin address range in vgacon_scroll()" (2025-08-02 21:47:33 +0200)
----------------------------------------------------------------
fbdev fixes for 6.17-rc1:
- Revert a patch which broke VGA console.
- Fix an out-of-bounds access bug which may happen during console
resizing when a console is mapped to a frame buffer.
----------------------------------------------------------------
Helge Deller (1):
Revert "vgacon: Add check for vc_origin address range in vgacon_scroll()"
Sravan Kumar Gundu (1):
fbdev: Fix vmalloc out-of-bounds write in fast_imageblit
drivers/video/console/vgacon.c | 2 +-
drivers/video/fbdev/core/fbcon.c | 9 +++++----
2 files changed, 6 insertions(+), 5 deletions(-)
next reply other threads:[~2025-08-07 11:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 11:21 Helge Deller [this message]
2025-08-08 3:59 ` [GIT PULL] fbdev last fixes for v6.17-rc1 pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aJSMS8PhMMe0NL63@p100 \
--to=deller@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).