From: Paulo Alcantara <pc@manguebit.org>
To: sorenson@redhat.com, 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 22:30:06 -0300 [thread overview]
Message-ID: <61168e3b796d424af9612ad9619ae95b@manguebit.org> (raw)
In-Reply-To: <8b7e30ff-fbd9-499e-b371-725c7b85a189@redhat.com>
Frank Sorenson <sorenson@redhat.com> writes:
> 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
Oh Frank, that's fine. No worries.
My only concern is that this SMB1 code, and as much as we can avoid it,
the better. The bugs are still valid to be reviewed and fixed, whether
we like it or not.
If we could have reproducers or any other way to validate them, great.
Otherwise, it's fine too -- we can fix any regressions later.
A few days ago we were struggling with getting diretory listing fixed
against Windows XP server because of a cleanup patch that touched SMB1
code that had been working for a very long time...
I'll help you with that. Great work.
prev parent reply other threads:[~2026-08-28 1:30 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
2026-08-28 1:30 ` Paulo Alcantara [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=61168e3b796d424af9612ad9619ae95b@manguebit.org \
--to=pc@manguebit.org \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=sorenson@redhat.com \
--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