https://bugs.kde.org/show_bug.cgi?id=508319
Bug ID: 508319
Summary: io_uring reads are not recognized as initializing
memory
Classification: Developer tools
Product: valgrind
Version First 3.25.0
Reported In:
Platform: Ubuntu
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: chris.m.mi...@gmail.com
Target Milestone: ---
Created attachment 184127
--> https://bugs.kde.org/attachment.cgi?id=184127&action=edit
C repro
SUMMARY
Reading into a buffer using io_uring and then subsequently accessing the buffer
is a reported as an uninitialized read.
STEPS TO REPRODUCE
1. Compile the attached C code (depends on liburing).
2. Run `valgrind ./a.out`, and enter any input.
3. memcheck reports uninitialized bytes in the write syscall.
OBSERVED RESULT
==2777862== Syscall param write(buf) points to uninitialised byte(s)
==2777862== at 0x4999574: write (write.c:26)
==2777862== by 0x400173C: main (in /home/chris/test)
==2777862== Address 0x1ffefffdbe is on thread 1's stack
==2777862== in frame #1, created by main (???:)
==2777862==
EXPECTED RESULT
No errors.
SOFTWARE/OS VERSIONS
Linux: 6.8.0 (Ubuntu 24.04)
Valgrind: 3.25.1
--
You are receiving this mail because:
You are watching all bug changes.
