> > Hello,
> >
> > I have an issue with rt_igb not working with an Intel I210 on ARM (see
> > system configuration below).
> > With Wireshark, looks like rtping is sending garbage on the network
> > (see below).
> > I notice there is no interrupt in /proc/xenomai/irq (see below).
> > Looks like oth
On 05.01.22 16:08, Bezdeka, Florian (T CED SES-DE) wrote:
> On Wed, 2022-01-05 at 15:58 +0100, Jan Kiszka wrote:
>> On 05.01.22 15:56, Bezdeka, Florian (T CED SES-DE) wrote:
>>> On Wed, 2022-01-05 at 15:43 +0100, Jan Kiszka wrote:
On 05.01.22 15:06, Florian Bezdeka wrote:
> Hi all,
>
>
On Wed, 2022-01-05 at 15:58 +0100, Jan Kiszka wrote:
> On 05.01.22 15:56, Bezdeka, Florian (T CED SES-DE) wrote:
> > On Wed, 2022-01-05 at 15:43 +0100, Jan Kiszka wrote:
> > > On 05.01.22 15:06, Florian Bezdeka wrote:
> > > > Hi all,
> > > >
> > > > this is the last missing POSIX related y2038 aff
On 05.01.22 15:56, Bezdeka, Florian (T CED SES-DE) wrote:
> On Wed, 2022-01-05 at 15:43 +0100, Jan Kiszka wrote:
>> On 05.01.22 15:06, Florian Bezdeka wrote:
>>> Hi all,
>>>
>>> this is the last missing POSIX related y2038 affected syscall in
>>> Xenomai. With this applied we have two Xenomai speci
On Wed, 2022-01-05 at 15:43 +0100, Jan Kiszka wrote:
> On 05.01.22 15:06, Florian Bezdeka wrote:
> > Hi all,
> >
> > this is the last missing POSIX related y2038 affected syscall in
> > Xenomai. With this applied we have two Xenomai specific syscalls
> > missing:
> >
> > - sc_cobalt_thread_sets
On 05.01.22 15:06, Florian Bezdeka wrote:
> Hi all,
>
> this is the last missing POSIX related y2038 affected syscall in
> Xenomai. With this applied we have two Xenomai specific syscalls
> missing:
>
> - sc_cobalt_thread_setschedparam_ex
> - sc_cobalt_thread_getschedparam_ex
>
> While addin
Initialization of the mutex used for mutex_timedlock64 tests could fail.
We have to abort the test in this case.
Signed-off-by: Florian Bezdeka
---
testsuite/smokey/y2038/syscall-tests.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/testsuite/smokey/y2038/syscall-tests.c
Like all other pointers in the cond_wait_prologue interface the error
pointer is user-provided and should be annotated accordingly.
Signed-off-by: Florian Bezdeka
---
kernel/cobalt/posix/cond.c | 8
kernel/cobalt/posix/cond.h | 8
kernel/cobalt/posix/syscall32.c | 4 +
It libc reports time64_t support, cond_wait_prologue is now dispatched
to the time64_t based syscall.
Signed-off-by: Florian Bezdeka
---
lib/cobalt/cond.c | 21 +
1 file changed, 17 insertions(+), 4 deletions(-)
diff --git a/lib/cobalt/cond.c b/lib/cobalt/cond.c
index 1bf5c7
According to the doctype provided by __get_user (which is used by the
__xn_get_user() macro) each call should be protected by access_ok().
We missed such a protection at some places.
Signed-off-by: Florian Bezdeka
---
kernel/cobalt/posix/internal.h | 4
kernel/cobalt/posix/nsem.c | 3
Extending the smokey testsuite to do some tests for the recently added
cond_wait_prologue64 syscall.
Signed-off-by: Florian Bezdeka
---
testsuite/smokey/y2038/syscall-tests.c | 97 ++
1 file changed, 97 insertions(+)
diff --git a/testsuite/smokey/y2038/syscall-tests.c
b
The following validation issues have been addressed:
- __cobalt_cond_wait_prologue() missed validating the supplied
pointers after the registry lookup which could fail. That triggered
the kernel OOPS dumped below
- The check removed from cobalt_cond_timedwait_prologue() is now
alr
Add a syscall specific for cond_wait_prologue64 with 64bit time_t.
Signed-off-by: Florian Bezdeka
---
include/cobalt/uapi/syscall.h | 1 +
kernel/cobalt/posix/cond.c | 26 ++
kernel/cobalt/posix/cond.h | 13 +
kernel/cobalt/posix/syscall3
Hi all,
this is the last missing POSIX related y2038 affected syscall in
Xenomai. With this applied we have two Xenomai specific syscalls
missing:
- sc_cobalt_thread_setschedparam_ex
- sc_cobalt_thread_getschedparam_ex
While adding tests for the introduced cond_wait_prologue64 I hit a
kernel
14 matches
Mail list logo