Re: Re: [PATCH v2] io_uring: Avoid polling configuration errors

[hexue]

>My stance is still the same - why add all of this junk just to detect a
>misuse of polled IO? It doesn't make sense to me, it's the very
>definition of "doctor it hurts when I do this" - don't do it.

>So unless this has _zero_ overhead or extra code, which obviously isn't
>possible, or extraordinary arguments exists for why this should be
>added, I don't see this going anywhere.

Actually, I just want users to know why they got wrong data, just a warning of an error,
like doctor tell you why you do this will hurt. I think it's helpful for users to use tools
accurately.
and yes, this should be as simple as possible, I'll working on it. I'm not sure if I made
myself clear and make sense to you?

--
hexue