Re: [PATCH 1/1] io_uring/zctx: separate notification user_data

[Pavel Begunkov <asml.silence@gmail.com>]

On 2/17/26 15:15, Jens Axboe wrote:
> On 2/17/26 8:03 AM, Pavel Begunkov wrote:
>> On 2/17/26 13:12, Jens Axboe wrote:
>>> On 2/17/26 4:15 AM, Pavel Begunkov wrote:
...
>>> The patch should just be removing that addr3 -EINVAL case, and adding
>>> the two lines that check IORING_SEND_ZC_NOTIF_USER_DATA, and if set, assign
>>> notif->cqe.user_data from addr3.
>>>
>>> But I object to saying this is a "degraded" uapi, to me it's very much a
>>> better one as it allows all values of user_data, rather than have some
>>> magic 0 value that's not valid for no other reason than force policy.
>>
>> Well, we clearly disagree on that one.
> 
> In the spirit of making progress and not wasting anymore time on this
> fairly fruitless discussion, I'm fine with adding the else branch, and
> hence v2 as-is.

Looks like it got lost / forgotten? I can't find it in for-next

-- 
Pavel Begunkov