[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87r04xdd93.fsf@oldenburg.str.redhat.com>
Date: Mon, 20 Jan 2025 10:51:36 +0100
From: Florian Weimer <fweimer@...hat.com>
To: Xi Ruoyao <xry111@...111.site>
Cc: Christian Brauner <brauner@...nel.org>, Aleksa Sarai
<cyphar@...har.com>, Ingo Molnar <mingo@...hat.com>, Peter Zijlstra
<peterz@...radead.org>, Juri Lelli <juri.lelli@...hat.com>, Vincent
Guittot <vincent.guittot@...aro.org>, Dietmar Eggemann
<dietmar.eggemann@....com>, Steven Rostedt <rostedt@...dmis.org>, Ben
Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>, Valentin
Schneider <vschneid@...hat.com>, Alexander Viro
<viro@...iv.linux.org.uk>, Jan Kara <jack@...e.cz>, Arnd Bergmann
<arnd@...db.de>, Shuah Khan <shuah@...nel.org>, Kees Cook
<kees@...nel.org>, Mark Rutland <mark.rutland@....com>,
linux-kernel@...r.kernel.org, linux-api@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-arch@...r.kernel.org,
linux-kselftest@...r.kernel.org, libc-alpha@...rceware.org
Subject: Re: [PATCH RFC v3 02/10] sched_getattr: port to copy_struct_to_user
* Xi Ruoyao:
>> > So should we drop the test before Glibc-2.41 release? I'm seeing the
>> > failure during my machine test.
>> I was waiting for a verdict from the kernel developers. I didn't expect
>> such a change to happen given the alleged UAPI policy.
>
> But 6.13 is already released without reverting the behavior change
> now... So is this the "final" verdict?
I had originally missed the Linux 6.13 release. I've submitted a glibc
patch:
[PATCH] Linux: Do not check unused bytes after sched_getattr in
tst-sched_setattr
<https://inbox.sourceware.org/libc-alpha/87v7u9ddas.fsf@oldenburg.str.redhat.com/>
Thanks,
Florian
Powered by blists - more mailing lists