[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230510143927.123170-1-ammarfaizi2@gnuweeb.org>
Date: Wed, 10 May 2023 21:39:25 +0700
From: Ammar Faizi <ammarfaizi2@...weeb.org>
To: Jens Axboe <axboe@...nel.dk>
Cc: Ammar Faizi <ammarfaizi2@...weeb.org>,
Barnabás Pőcze <pobrn@...tonmail.com>,
Michael William Jonathan <moe@...weeb.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
io-uring Mailing List <io-uring@...r.kernel.org>,
GNU/Weeb Mailing List <gwml@...r.gnuweeb.org>
Subject: [PATCH liburing v1 0/2] 2 fixes for recv-msgall.c
Hi Jens,
This is the follow up patchset for the recent issue found in
recv-msgall.c. There are two patches in this series.
1. Fix undefined behavior in `recv_prep()`.
The lifetime of `struct msghdr msg;` must be long enough until the CQE
is generated because the recvmsg operation will write to that storage. I
found this test segfault when compiling with -O0 optimization. This is
undefined behavior and may behave randomly. Fix this by making the
lifetime of `struct msghdr msg;` long enough.
2. Fix invalid mutex usage.
Calling pthread_mutex_lock() twice with the same mutex in the same
thread without unlocking it first is invalid. The intention behind this
pattern was to wait for the recv_fn() thread to be ready. Use the
pthread barrier instead. It is more straightforward and correct.
Please apply!
Signed-off-by: Ammar Faizi <ammarfaizi2@...weeb.org>
---
Ammar Faizi (2):
recv-msgall: Fix undefined behavior in `recv_prep()`
recv-msgall: Fix invalid mutex usage
test/recv-msgall.c | 44 +++++++++++++++++++++-----------------------
1 file changed, 21 insertions(+), 23 deletions(-)
base-commit: 4961ac480052089a94978e9f771d513551aff61b
--
Ammar Faizi
Powered by blists - more mailing lists