Re: [PATCH v3] misc: mei: fix race condition between client teardown and read completion

[gregkh@xxxxxxxxxxxxxxxxxxx]

On Mon, Aug 24, 2026 at 11:00:15AM +0000, nirbhayykumarr@xxxxxxxxx wrote:
> Hi Greg,

Hi, but please don't top-post, that's not good email etiquette :)

And please wrap your lines, I have done so manually below so we can read
them...

> To answer your first question directly: Yes, I used an LLM to help
> polish my changelog and commit description, and learn the strict
> kernel mailing list etiquette. This is my very first kernel
> contribution, and I used it to help navigate the patching process.
> However, the core technical work, finding the bug, root causing it,
> writing the C patch, and testing it is entirely my own.

That's great, but as you used a LLM, please document it as such.

> Regarding how this was found: This came out of a broader research
> project centered around systematic fuzzing and interface testing of
> /dev/mei0. As part of testing various subsystem boundaries, I wrote a
> custom multi-threaded C stress utility that rapidly hammers the
> driver, more specifically, one thread streaming asynchronous MKHI
> requests while a second thread concurrently drives rapid
> open/close/reconnect cycles.

Great, fuzzers are nice, you should explain that in the changelog as
well.

thanks,

greg k-h