From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Denis Arefev <arefev@swemel.ru>
Cc: deller@gmx.de, dri-devel@lists.freedesktop.org,
jani.nikula@intel.com, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org, lvc-project@linuxtesting.org,
tzimmermann@suse.de
Subject: Re: [PATCH 1/1] fbdev: atyfb: Fix buffer overflow
Date: Tue, 1 Apr 2025 19:26:46 +0300 [thread overview]
Message-ID: <Z-wTxsV9C9MzoXl9@intel.com> (raw)
In-Reply-To: <20250401102330.7759-1-arefev@swemel.ru>
On Tue, Apr 01, 2025 at 01:23:30PM +0300, Denis Arefev wrote:
> > It's old, but still runs in some configurations and people
> > still (although probably not on daily bases) use it.
> > Also don't forget about the various old non-x86 hardware machines
> > which often used ATI cards too, and those machines are still
> > supported by Linux as well.
>
> Hi Helge.
> Thanks for the reply.
>
> Ok. Everyone agrees that there is an error (buffer overflow
> lt_lcd_regs[LCD_MISC_CNTL]).
As I said, that will never happen.
> Ok. Everyone agrees that this code is still needed.
>
> Then I propose to fix this error. :)
>
> Unfortunately, I can't do everything by the rules, I didn't save
> the chip datasheet. (I didn't think I would ever need it again.).
>
> Regards Denis.
--
Ville Syrjälä
Intel
prev parent reply other threads:[~2025-04-01 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 10:01 [PATCH 0/1] fbdev: atyfb: Fix buffer overflow Denis Arefev
2025-03-27 10:01 ` [PATCH 1/1] " Denis Arefev
2025-03-27 10:14 ` Jani Nikula
2025-03-31 19:55 ` Ville Syrjälä
2025-04-01 8:40 ` Denis Arefev
2025-04-01 9:03 ` Helge Deller
2025-04-01 10:23 ` Denis Arefev
2025-04-01 16:26 ` Ville Syrjälä [this message]
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=Z-wTxsV9C9MzoXl9@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=arefev@swemel.ru \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=tzimmermann@suse.de \
/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).