From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Wed, 5 Jan 2022 15:58:42 +0100 MIME-Version: 1.0 Subject: Re: [PATCH 0/7] y2038: cond_wait_prologue64 and related fixes Content-Language: en-US References: <20220105140650.1033850-1-florian.bezdeka@siemens.com> <13d8cb9c-591d-481a-73b6-623b892deea0@siemens.com> From: Jan Kiszka In-Reply-To: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Bezdeka, Florian (T CED SES-DE)" , "xenomai@xenomai.org" 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 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 OOPS due to insuficient validation of user provided pointers. >>> That has been addressed as well. >> >> Thanks for both! Is it possibly to move the fixes the front? That would >> also ensure that I can easily pick them into stable. > > Yes. Patch 4 and 7 could be moved to the front easily. Do you want me > to split patch 2 into the y2038 and non y2038 part, or does that not > qualify for stable at all? Can I reorder things myself, or does patch 4 break (patch 7 does not, already checked)? Then I just change the application order while doing git am. Jan -- Siemens AG, Technology Competence Center Embedded Linux