mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Eli Billauer <eli.billauer@gmail.com>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] char: xillybus: Harden driver and improve code quality
Date: Fri, 17 Jul 2026 16:04:04 +0200	[thread overview]
Message-ID: <2026071734-undertake-train-f9f6@gregkh> (raw)
In-Reply-To: <20260630092330.43534-1-eli.billauer@gmail.com>

On Tue, Jun 30, 2026 at 11:23:23AM +0200, Eli Billauer wrote:
> This patch set consists of several boundary and sanity checks, gaining
> better control of execution flow and fixing minor coding issues. No
> difference is expected in the driver's behavior under normal conditions,
> except for one change that might improve bandwidth performance
> marginally.
> 
> Why all of the sudden? These patches are the result of a comprehensive
> AI-assisted code review, using Deepseek, Kimi Thinking K2.6, ChatGPT,
> and Claude Sonnet 4.6 as plain prompt tools.
> 
> I've spent three weeks in what I call a "reverse rubber duck" session,
> asking these LLMs to find bugs in the code and following up on different
> leads, the vast majority of which turned out to be no more than quack.
> Occasionally the points made by AI were valid, and in others, the mere
> effort to explain why the remark is wrong to the rubber duck led to
> finding real issues.
> 
> Almost none of the fixes suggested by AI were even near the actual
> corrections in this patch set.

I get the following build warning/break when applying these:

drivers/char/xillybus/xillybus_class.c:74:7: error: variable 'rc' is used uninitialized whenever 'if' condition is true [-Werror,-Wsometimes-uninitialized]
   74 |                 if (i > 99) {
      |                     ^~~~~~
drivers/char/xillybus/xillybus_class.c:179:9: note: uninitialized use occurs here
  179 |         return rc;
      |                ^~
drivers/char/xillybus/xillybus_class.c:74:3: note: remove the 'if' if its condition is always false
   74 |                 if (i > 99) {
      |                 ^~~~~~~~~~~~~
   75 |                         dev_err(dev, "Failed to obtain unique unit name\n");
      |                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   76 |                         goto fail_obtain;
      |                         ~~~~~~~~~~~~~~~~~
   77 |                 }
      |                 ~
drivers/char/xillybus/xillybus_class.c:51:8: note: initialize the variable 'rc' to silence this warning
   51 |         int rc;
      |               ^
      |                = 0
1 error generated.

Can you fix that up?

thanks,

greg k-h

      parent reply	other threads:[~2026-07-17 14:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30  9:23 Eli Billauer
2026-06-30  9:23 ` [PATCH 1/7] char: xillybus: Improve control of execution flow with mutexes Eli Billauer
2026-06-30  9:23 ` [PATCH 2/7] char: xillybus: Remove duplicate error path code Eli Billauer
2026-06-30  9:23 ` [PATCH 3/7] char: xillybus: Avoid possible bandwidth inefficiency Eli Billauer
2026-06-30  9:23 ` [PATCH 4/7] char: xillybus: Use unsigned arithmetic for jiffies differences Eli Billauer
2026-06-30  9:23 ` [PATCH 5/7] char: xillybus: Integer arithmetic improvements Eli Billauer
2026-06-30  9:23 ` [PATCH 6/7] char: xillybus: Add defensive sanity checks Eli Billauer
2026-06-30  9:23 ` [PATCH 7/7] char: xillybus: Ignore and report unsolicited interrupts Eli Billauer
2026-07-17 14:04 ` Greg KH [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=2026071734-undertake-train-f9f6@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=eli.billauer@gmail.com \
    --cc=linux-kernel@vger.kernel.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