diff options
| author | Jens Axboe <axboe@kernel.dk> | 2021-09-03 16:55:26 -0600 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2021-09-03 16:59:06 -0600 |
| commit | 2fc2a7a62eb58650e71b4550cf6fa6cc0a75b2d2 (patch) | |
| tree | c5ad51871bb336283d9a08051cfbcca4497fa9b5 /lib/test_fortify/write_overflow-memcpy.c | |
| parent | 31efe48eb5dc4de3e31e84b54f287e9665410ab3 (diff) | |
io_uring: io_uring_complete() trace should take an integer
It currently takes a long, and while that's normally OK, the io_uring
limit is an int. Internally in io_uring it's an int, but sometimes it's
passed as a long. That can yield confusing results where a completions
seems to generate a huge result:
ou-sqp-1297-1298 [001] ...1 788.056371: io_uring_complete: ring 000000000e98e046, user_data 0x0, result 4294967171, cflags 0
which is due to -ECANCELED being stored in an unsigned, and then passed
in as a long. Using the right int type, the trace looks correct:
iou-sqp-338-339 [002] ...1 15.633098: io_uring_complete: ring 00000000e0ac60cf, user_data 0x0, result -125, cflags 0
Cc: stable@vger.kernel.org
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'lib/test_fortify/write_overflow-memcpy.c')
0 files changed, 0 insertions, 0 deletions