Re: [PATCH v5 2/2] xfs: prevent close() from hanging on frozen filesystems

On Sat, Aug 15, 2026 at 2:39 PM Carlos Maiolino <[email protected]> wrote:

> Darrick spent his time reviewing your patch. You used a LLM model to
> reply his email which I already find disrespectful enough, and worse,
> you didn't even check the result? Why do you delegate to others your
> responsibility to review your content? If you didn't understand the
> generated content, that would already be a red flag that you shouldn't
> be sending it. If you thought it was right, it means you didn't check it
> carefully enough as you didn't even add any information saying you got
> this from a LLM and wasn't sure how right the information was.
>
> We are all overwhelmed with the inflow of patches now that writing them
> has never been easier.... Yet, we dedicate our time and effort reviewing
> them in an effort to keep the project's quality high. And yet we have
> just so much time in our hands and we would appreciate a little respect
> with at least reviewing the garbage you generated.
>
> You can use whatever tool you want to generate the patches, but Linux
> policy has been that YOU are responsible for whatever you wrote with
> whatever tool you use.
>
> And yet, I can't really emphasize how disrespectful I think such attitude
> is. Somebody's using a LLM to reply to somebody's else emails/messages,
> to say the least, make me believe you think your time is much more valuable
> than ours, giving you didn't even bother to review the email you sent to
> Darrick.
>
> Carlos
>

Darrick, Carlos,

You are completely right, and I apologize.

Because the original patch was carefully crafted came from Christoph's,
suggestion and reviewed thoroughly, I failed to give Darrick’s feedback
the careful attention it deserved and sent a reply without verifying the
locking logic against the codebase. That was disrespectful of
your time and effort, even though the intention was never that, but no
amount of reasoning can justify that and I take full responsibility for it.

I will step back, study the locking paths in the codebase properly,
and ensure any future submissions or replies are thoroughly verified.

Thanks,
Aditya