On Tue, Aug 2, 2022 at 3:24 PM Jens Axboe <axboe@xxxxxxxxx> wrote:
>
> I take it this is only happening on clang, which is why I haven't seen
> it as I don't compile with clang.
It happens both with clang-14.0 and with gcc-12.1.1.
And Keith says that the issue was apparently know about and fixed over
two weeks ago.
So *somebody* knew about it, and fixed it, but apparently the people
involved didn't bother informing upstream.
Regardless of what happened, it's not even remotely acceptable.
Linus
