Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Frank Sorenson <sorenson@redhat.com>
To: Paulo Alcantara <pc@manguebit.org>, linux-cifs@vger.kernel.org
Cc: linkinjeon@kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] smb: client: tighten validate_t2() offset bounds against actual buffer size
Date: Thu, 27 Aug 2026 08:45:15 -0500	[thread overview]
Message-ID: <8b7e30ff-fbd9-499e-b371-725c7b85a189@redhat.com> (raw)
In-Reply-To: <f67877e37eeede299fbbe86914cd58f2@manguebit.org>

On 8/26/26 6:03 PM, Paulo Alcantara wrote:
> Besides all these LLM-generated messages and comments, would you have a
> reproducer or a real use case that would require such changes?

I just want to apologize for going so far overboard.  I identified a
potential type of issue, and then kept expanding the scope without
finding a concrete problem or reproducer.  That's a definite
overcorrection; I tried to fix things that have no known impact in
practice ('malicious SMB1 server' is a pretty weak threat).

And as you noted, I relied too heavily on AI assistance; that's on
me.  I'll be more careful about both the scope of what I do and how
I get there.

I'll obviously withdraw this

Frank
-- 
Frank Sorenson
sorenson@redhat.com
Principal Software Maintenance Engineer, filesystems
Red Hat


  reply	other threads:[~2026-08-27 13:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25  3:09 [PATCH] smb: client: tighten validate_t2() offset bounds against actual buffer size Frank Sorenson
2026-08-26 23:03 ` Paulo Alcantara
2026-08-27 13:45   ` Frank Sorenson [this message]
2026-08-28  1:30     ` Paulo Alcantara

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=8b7e30ff-fbd9-499e-b371-725c7b85a189@redhat.com \
    --to=sorenson@redhat.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=pc@manguebit.org \
    --cc=stable@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