Linux filesystem development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Enjoy the Summer!
Date: Fri, 3 Jul 2026 09:01:57 -0700	[thread overview]
Message-ID: <20260703160157.GA9368@frogsfrogsfrogs> (raw)
In-Reply-To: <20260703-vfs-summer-jam-22b2edbbbc44@brauner>

On Fri, Jul 03, 2026 at 05:34:52PM +0200, Christian Brauner wrote:
> Hey!
> 
> Summer is here and many core developers and maintainers will be taking
> vacations during July and August. I hope everyone gets some
> well-deserved rest and recharge and can step away from the fray a little
> bit.
> 
> The VFS tree will remain open but expect delays in patch processing.
> Please don't spam our few overloaded maintainers and reviewers
> unnecessarily.

<nod>

> As with other subsystems we see a lot of AI generated patches and bug
> reports (publicly and off-list) where the submitter functions like the
> Mouth of Sauron. This is not acceptable and such patches will either be
> ignored or heavily deprioritized.
> 
> In general, over-the-wall, vibe-coded, complex RFC submissions can never
> be expected to get lenghty, in-depth reviews especially if the submitter
> shows clear signs of not having actually spent the time to think things
> through or doesn't understand what they are working on. This is just
> taking up valuable development and review time.
> 
> Throwing mountains of code or an endless firehose of tiny patches over
> the wall to get your name into the kernel is not a success story.
> 
> On a postivie note, the last months review discipline has improved quite
> a bit in my opinion.

I'm glad to hear this!

>                      But I want to emphasize once more that regular
> contributors especially with lenghty submissions to the subsystem are
> expected to take part in review.
> 
> Review doesn't have to only mean "look for memory leaks". We know that
> LLMs are suprisingly good at finding various issues. They have no taste
> however. So review should focus on maintainability and design with the
> longevity of the subsystem in mind - both internal and external apis.

+1

FWIW, $LLM has been quite good at finding coding errors in xfs and
xfsprogs.  However, I observed that as soon as I started asking it to
review design documentation and to examine maintainability, the tone of
the emitted output switched from cloying to redditsnark ("I wouldn't
call this **good**..."). :P

> Keep up the good work and enjoy the summer!

You as well!

--D

      reply	other threads:[~2026-07-03 16:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-03 15:34 Enjoy the Summer! Christian Brauner
2026-07-03 16:01 ` Darrick J. Wong [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=20260703160157.GA9368@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=brauner@kernel.org \
    --cc=linux-fsdevel@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