From: Helge Deller <deller@gmx.de>
To: Albin Babu Varghese <albinbabuvarghese20@gmail.com>
Cc: Simona Vetter <simona@ffwll.ch>,
syzbot+48b0652a95834717f190@syzkaller.appspotmail.com,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds
Date: Wed, 1 Oct 2025 20:36:47 +0200 [thread overview]
Message-ID: <5ab00319-e43e-4000-8814-c7d67f384c53@gmx.de> (raw)
In-Reply-To: <aN1ihRfB-GHTEt_4@arch-box>
On 10/1/25 19:19, Albin Babu Varghese wrote:
> Hi Helge, Thanks for the review.
>
>> I wonder if the image.height value should be capped in this case,
>> instead of not rendering any chars at all?
>> Something like (untested!):
>>
>> + if (image.dy >= info->var.yres)
>> + return;
>> + image.height = min(image.height, info->var.yres - image.dy);
>
> This looks like a better implementation than what I had.
I just added comments - not sure if mine was better.,
> I thought it might be better to skip the entire row instead of
> rendering partially.
Do you know if this affects the selection?
If so, would modifying (reducing/shortening) the selection maybe fix it?
> I’m still new to this subsystem, so thanks for pointing this out.
> I’ll test the suggested changes and send a v2.
Thanks for testing and checking!
Helge
next prev parent reply other threads:[~2025-10-01 18:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-27 7:50 [PATCH] fbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds Albin Babu Varghese
2025-09-30 20:46 ` Helge Deller
2025-10-01 17:19 ` Albin Babu Varghese
2025-10-01 18:36 ` Helge Deller [this message]
2025-10-02 8:52 ` Albin Babu Varghese
2025-10-02 10:11 ` Helge Deller
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=5ab00319-e43e-4000-8814-c7d67f384c53@gmx.de \
--to=deller@gmx.de \
--cc=albinbabuvarghese20@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=syzbot+48b0652a95834717f190@syzkaller.appspotmail.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