Hello,
I've noticed that with the uclibc-ng 1.0.39 the tests tst-cancel18 and
tst-cancelx18 are failing in NPTL-enabled configs (on xtensa).
Bisection pointed me to the commit
08d46f1ce21e ("librt: avoid compilation error")
which effectively turned off cancellation for clock_nanosleep.
Reverting it fixes the tests for me, and does not break uclibc-ng
build on nommu configs with or without threads support.
So I'm curious what was the original issue that mentioned commit
tried to solve (what arch/config)?
--
Thanks.
-- Max
I'm having an issue with the new 'prlimit' additions to 1.0.40. One of
my targets runs an older kernel that predates the prlimit64 syscall. I
sent in patch that guards around that code, though it would still be
defined in headers and probably still cause me issues.
My other target uses kernel 2.6.36.4, which should include the syscall,
but I get an error the same as this github issue.
https://github.com/util-linux/util-linux/commit/01e94325e676f36b364032a6f5a…
Also, when I try to compile sample program that target:
#include <sys/types.h>
#include <sys/time.h>
#include <sys/resource.h>
#include <stddef.h>
int main ()
{
int ret;
ret = prlimit(0, RLIMIT_AS, NULL, NULL);
if (ret != 0) {
return 1;
};
return 0;
}
I get error
prlimit.c:10:11: warning: implicit declaration of function ‘prlimit’;
did you mean ‘setrlimit’? [-Wimplicit-function-declaration]
10 | ret = prlimit(0, RLIMIT_AS, NULL, NULL);
| ^~~~~~~
| setrlimit
on unpatched uclibc-ng like symbols still aren't being visible.
thanks,
Lance Fredrickson
Greetings,
We have received a report that indicates that one of your products contains a vulnerability. In the interest of coordinated disclosure (which aims to address vulnerabilities before they can be exploited by attackers), we would like to communicate this information to you.
To view the details associated with this case, please visit https://kb.cert.org/vince/ and create an account on VINCE, which is our coordination platform. Within VINCE, it is possible to view the original vulnerability report. VINCE also facilitates direct communication with the reporter, pending the reporter's willingness to communicate about the case.
If you need to reply to this email, please do not alter the VU# in the subject line to ensure that your message is routed properly on our end.
Regards,
Vulnerability Analysis Team
======================================================================
CERT Coordination Center
kb.cert.org / cert(a)cert.org
======================================================================
-----Original Message-----
From: Waldemar Brodkorb <wbx(a)uclibc-ng.org>
Sent: Tuesday, February 1, 2022 1:21 PM
To: Timur David Snoke <tdsnoke(a)cert.org>
Cc: 'devel(a)uclibc-ng.org' <devel(a)uclibc-ng.org>
Subject: Re: [uclibc-ng-devel] Vulnerability in uClibc-ng and also uClibc
Hi Timur,
Timur David Snoke wrote,
> Greetings,
>
>
>
> We have a reported vulnerability in both this library and the
> unmaintained one, how can we communicate this to the developers?
>
>
>
> Regards,
sent an email to the list.
best regards
Waldemar
Greetings,
We have a reported vulnerability in both this library and the unmaintained one, how can we communicate this to the developers?
Regards,
Vulnerability Analysis Team
======================================================================
CERT Coordination Center
kb.cert.org / cert(a)cert.org<mailto:cert@cert.org>
======================================================================
From: Sergey Matyukevich <sergey.matyukevich(a)synopsys.com>
When MD_FALLBACK_FRAME_STATE_FOR handler in libgcc unwind code checks
the second instruction opcode in __default_rt_sa_restorer function,
it expects to see the following values for ARC cores:
- 0x7ee0781e for ARCv2 LE
- 0x003f226f for ARC700 LE
ARC700 value correspond to trap0 instruction. ARCv2 value corresponds
to the following code:
traps_0
j_s [blink]
However, unlike glibc, uClibc implementation of __default_rt_sa_restorer
for ARC does not have that jump. Hence libgcc unwind code is not able
to recognize signal frame correctly on ARCv2 and completes too early.
This change fixes libgcc unwinding over signal frame on ARCv2 adding
missing jump to __default_rt_sa_restorer.
Signed-off-by: Sergey Matyukevich <sergey.matyukevich(a)synopsys.com>
---
libc/sysdeps/linux/arc/sigrestorer.S | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/libc/sysdeps/linux/arc/sigrestorer.S b/libc/sysdeps/linux/arc/sigrestorer.S
index e4deb6bd4..60d35ab3e 100644
--- a/libc/sysdeps/linux/arc/sigrestorer.S
+++ b/libc/sysdeps/linux/arc/sigrestorer.S
@@ -1,5 +1,5 @@
/*
- * Copyright (C) 2017 Synopsys, Inc. (www.synopsys.com)
+ * Copyright (C) 2017-2022 Synopsys, Inc. (www.synopsys.com)
*
* Licensed under the LGPL v2.1 or later, see the file COPYING.LIB in this tarball.
*/
@@ -22,4 +22,5 @@
__default_rt_sa_restorer:
mov r8, __NR_rt_sigreturn
ARC_TRAP_INSN
+ j_s [blink]
--
2.34.1