public inbox for drm-ai-reviews@public-inbox.freedesktop.org
 help / color / mirror / Atom feed
From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: Re: [PATCH 03/35] fbdev: sisfb: Use safer strscpy() instead of strcpy()
Date: Tue, 28 Apr 2026 15:38:39 +1000	[thread overview]
Message-ID: <review-patch3-ccd01f97-d4b7-4bd0-92c1-adc3b1136cbc@gmx.de> (raw)
In-Reply-To: <ccd01f97-d4b7-4bd0-92c1-adc3b1136cbc@gmx.de>

Patch Review

**Files:** `sis/sis_main.c` — 8 replacements

The 7 `ivideo->myid` replacements (e.g., `"SiS 730"` → `char myid[40]`) are trivially safe.

**Worth noting:** The `strbuf1` case is qualitatively different from the rest of the series:

```c
if(strlen(name) <= 19) {
    strscpy(strbuf1, name);
```

Here `strbuf1` is `char[20]` and the source is a runtime variable `name`, not a compile-time literal. The `strlen(name) <= 19` guard means the original `strcpy()` was already safe, but `strscpy()` adds defense-in-depth. This is genuinely a different pattern from copying a known-short literal into a known-large buffer — the commit message should acknowledge this rather than claiming all changes are identical.

**Reviewed-by: acceptable with nit**

---

---
Generated by Claude Code Patch Reviewer

  parent reply	other threads:[~2026-04-28  5:38 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-25  6:58 [PATCH 00/35] Use safer strscpy() instead of strcpy() Ai Chao
2026-04-25  6:58 ` [PATCH 01/35] fbdev: matroxfb: " Ai Chao
2026-04-28  5:38   ` Claude review: " Claude Code Review Bot
2026-04-25  6:58 ` [PATCH 02/35] fbdev: i810: " Ai Chao
2026-04-28  5:38   ` Claude review: " Claude Code Review Bot
2026-04-25  6:58 ` [PATCH 03/35] fbdev: sisfb: " Ai Chao
2026-04-25  8:08   ` Helge Deller
2026-04-25 11:02     ` David Laight
2026-04-28  5:38     ` Claude Code Review Bot [this message]
2026-04-25  6:58 ` [PATCH 04/35] fbdev: geode: " Ai Chao
2026-04-28  5:38   ` Claude review: " Claude Code Review Bot
2026-04-25  6:58 ` [PATCH 05/35] fbdev: atafb: " Ai Chao
2026-04-28  5:38   ` Claude review: " Claude Code Review Bot
2026-04-25  6:58 ` [PATCH 06/35] fbdev: tdfxfb: " Ai Chao
2026-04-28  5:38   ` Claude review: " Claude Code Review Bot
2026-04-25  6:58 ` [PATCH 07/35] fbdev: pm2fb: " Ai Chao
2026-04-28  5:38   ` Claude review: " Claude Code Review Bot
2026-04-25  6:58 ` [PATCH 08/35] fbdev: xen-fbfront: " Ai Chao
2026-04-28  5:38   ` Claude review: " Claude Code Review Bot
2026-04-25  6:59 ` [PATCH 09/35] fbdev: controlfb: " Ai Chao
2026-04-28  5:38   ` Claude review: " Claude Code Review Bot
2026-04-25  6:59 ` [PATCH 10/35] fbdev: stifb: " Ai Chao
2026-04-28  5:38   ` Claude review: " Claude Code Review Bot
2026-04-25  6:59 ` [PATCH 11/35] fbdev: fm2fb: " Ai Chao
2026-04-28  5:38   ` Claude review: " Claude Code Review Bot
2026-04-25  6:59 ` [PATCH 12/35] fbdev: arkfb: " Ai Chao
2026-04-28  5:38   ` Claude review: " Claude Code Review Bot
2026-04-25  6:59 ` [PATCH 13/35] fbdev: vt8500lcdfb: " Ai Chao
2026-04-28  5:38   ` Claude review: " Claude Code Review Bot
2026-04-25  6:59 ` [PATCH 14/35] fbdev: vt8623fb: " Ai Chao
2026-04-28  5:38   ` Claude review: " Claude Code Review Bot
2026-04-25  6:59 ` [PATCH 15/35] fbdev: gbefb: " Ai Chao
2026-04-28  5:38   ` Claude review: " Claude Code Review Bot
2026-04-25  6:59 ` [PATCH 16/35] fbdev: wm8505fb: " Ai Chao
2026-04-28  5:38   ` Claude review: " Claude Code Review Bot
2026-04-25  6:59 ` [PATCH 17/35] fbdev: rivafb: " Ai Chao
2026-04-28  5:38   ` Claude review: " Claude Code Review Bot
2026-04-25  6:59 ` [PATCH 18/35] fbdev: sh7760fb: " Ai Chao
2026-04-28  5:38   ` Claude review: " Claude Code Review Bot
2026-04-25  6:59 ` [PATCH 19/35] fbdev: savage: " Ai Chao
2026-04-28  5:38   ` Claude review: " Claude Code Review Bot
2026-04-28  5:38 ` Claude review: " Claude Code Review 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=review-patch3-ccd01f97-d4b7-4bd0-92c1-adc3b1136cbc@gmx.de \
    --to=claude-review@example.com \
    --cc=dri-devel-reviews@example.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