From: Yann Sionneau <ysionneau(a)kalrayinc.com>
Without this patch, since https://github.com/torvalds/linux/commit/dcd46d897adb70d63e025f175a00a89797…
this test runs in infinite loop.
Signed-off-by: Yann Sionneau <ysionneau(a)kalrayinc.com>
test/unistd/exec-null.c | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/test/unistd/exec-null.c b/test/unistd/exec-null.c
index 3df99f3..0f79b3d 100644
@@ -4,7 +4,12 @@
int main(int argc, char *argv)
- if (argc == 0)
+ /* since Linux https://github.com/torvalds/linux/commit/dcd46d897adb70d63e025f175a00a89797…
+ * kernel forces an empty first arg if execve is called
+ * with argv == NULL.
+ * so we need to handle argc == 1 for newer kernel as well
+ if (argc == 0 || argc == 1)
char *exec_argv, *exec_envp;
On 2023/06/07 23:57, Yann Sionneau wrote:
> Hello uClibc-ng hackers, Damien, Rich,
> I am sending this email to discuss the possibility to revert
> I think this change is wrong, I have been tracking an issue for a few
> days and I am pretty sure the issue comes from this commit.
> Basically what happens is that with this commit, tst-cancel18 test is
> The test is available over there:
> The reason for this fail is that clock_nanosleep code from libc is badly
> Because SINGLE_THREAD_P is actually defined, in case your libc build
> supports NPTL threads (which is, I think, the majority of configs,
> except very old systems using LINUXTHREADS or NOMMU maybe).
> In my case (kvx arch):
> #define SINGLE_THREAD_P __builtin_expect (THREAD_GETMEM (THREAD_SELF,
> header.multiple_threads) == 0, 1)
> This results to clock_nanosleep code being compiled to a very simple
> version that directly calls the syscall and does not change at all the
> thread cancellability to asynchronous before calling the syscall.
> Therefore, when the test main thread calls pthread_cancel(), no signal
> is sent (see
> and therefore the nanosleep syscall is never interrupted and the test fails.
> clock_nanosleep is defined to be a mandatory cancellation point by
> POSIX, it must be interruptible in all cases by pthread_cancel, whether
> in synchronous or asynchronous mode.
> I think the fix for the NOMMU case should be different, maybe checking
> for if LIBC_CANCEL_ASYNC is defined ?
> Damien do you have time to work on a new fix for the NOMMU case? Are you
> OK with the revert?
Not OK with a revert as that will bring back the compilation errors for RISC-V
Instead, please work on a fix for your case on top of the current code. If I
recall correctly, the code around this is rather messy with lots of ifdefs,
which may be why this regression was introduced. Cleaning up the code first to
avoid that may help avoiding further issues in the future.
Note that to test patches/regressions for risc-v NOMMU builds, you can simply
use buildroot and run:
To check that it builds.
> Can someone confirm my analysis here?
> Best regards,
Damien Le Moal
Western Digital Research