Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Gu Bowen <gubowen5@huawei.com>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Lu Jialin <lujialin4@huawei.com>
Subject: Re: [PATCH stable] fbdev: Fix out-of-bounds issue in sys_fillrect()
Date: Tue, 2 Dec 2025 21:05:22 +0100	[thread overview]
Message-ID: <aef7d5fd-2926-4c58-b720-4af58aa380d3@gmx.de> (raw)
In-Reply-To: <224e4e5b-14ae-411c-ad6c-f73c3b946ff8@huawei.com>

On 12/1/25 10:25, Gu Bowen wrote:
> Hi,
> 
> On 11/15/2025 3:21 AM, Helge Deller wrote:
>> 
>> That patch does not apply to git head. Can you try to reproduce
>> with git head?
>> 
> 
> fbdev has already been refactored by commit eabb03293087 ("fbdev:
> Refactoring the fbcon packed pixel drawing routines") on v6.15-rc1,
> so this issue no longer exists in the mainline version. Similar
> question has occurred in the past:
> 
> https://syzkaller.appspot.com/bug?extid=66bde8e1e4161d4b2cca
> 
> After the refactoring patch was merged, this issue did not reappear,
> but it still exists in the stable version.
Backporting commit eabb03293087 to 6.6 seems unrealistic.
So, maybe adding your patch to stable might make sense.

+	if (dst_offset < 0 || dst_offset >= p->fix.smem_len) {
+		pr_err("dst offset out of bound: dst_offset(%ld)", dst_offset);
+		return;

I don't like the pr_err() in here. I do understand that you want to print
that something wrong happened, but we are inside the console printing code.
I think we should just return in this case.

With that change we might ask Greg if he accepts this small patch for stable-6.6...

Helge

  reply	other threads:[~2025-12-02 20:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-12  7:32 [PATCH stable] fbdev: Fix out-of-bounds issue in sys_fillrect() Gu Bowen
2025-11-14 19:21 ` Helge Deller
2025-12-01  9:25   ` Gu Bowen
2025-12-02 20:05     ` Helge Deller [this message]
2025-12-03  2:11       ` Gu Bowen

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=aef7d5fd-2926-4c58-b720-4af58aa380d3@gmx.de \
    --to=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gubowen5@huawei.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=lujialin4@huawei.com \
    /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