From: "Theodore Tso" <tytso@mit.edu>
To: Matthew Wilcox <willy@infradead.org>
Cc: joreag@ulshe.ai, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [SECURITY / STATIC AUDIT] 44 CRITICAL/HIGH Open Manifold(s) in `Documentation/.renames.txt` (linux-master 7.4rc)
Date: Thu, 5 Nov 2026 10:46:53 -0500 [thread overview]
Message-ID: <auykRKL8SMW-bL60@mit.edu> (raw)
In-Reply-To: <autfQA_BKenrDFQY@casper.infradead.org>
On Wed, Nov 04, 2026 at 04:37:20PM -0500, Matthew Wilcox wrote:
> On Wed, Nov 04, 2026 at 04:25:09PM +0000, joreag@ulshe.ai wrote:
> > Hello Maintainer(s) of `Documentation/.renames.txt`:
> >
> > During an automated topological boundary audit of `linux-master (2)` using
> > Logic Archaeologist Pro (v8.5),
> > we identified 44 CRITICAL/HIGH Open Topological Manifold(s) in
> > `Documentation/.renames.txt` that may warrant review.
>
> If this is a joke, it's not very funny.
>
> If it's not a joke, you're an idiot.
My guess is option 2. It looks like this is an AI Slop startup:
https://ulshe.ai/products_archaeologist.html
... and this AI Slop tool doesn't realize that .renames.txt is a file
which is generated locally, and it is not part of the git repository.
If that is a "security vulnerability" or a "Topological Manifold
Closure" (whatever the hell that is) then any generated shell script
or compiled binary would be a "Manifold vulnerability" (again,
whatever the hell that is).
- Ted
prev parent reply other threads:[~2026-11-05 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 16:25 [SECURITY / STATIC AUDIT] 44 CRITICAL/HIGH Open Manifold(s) in `Documentation/.renames.txt` (linux-master 7.4rc) joreag
2026-11-04 16:37 ` Matthew Wilcox
2026-11-05 15:46 ` Theodore Tso [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=auykRKL8SMW-bL60@mit.edu \
--to=tytso@mit.edu \
--cc=corbet@lwn.net \
--cc=joreag@ulshe.ai \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.