linux-kernel - Re: [PATCH v2 2/3] selftests: Fix errno checking in syscall_user

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACT4Y+aoHwF8JtsdGXjozmUXgUX=_+HqML97KqF6-fDFiD57tA@mail.gmail.com>
Date: Sat, 8 Mar 2025 10:57:36 +0100
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Gregory Price <gourry@...rry.net>
Cc: krisman@...labora.com, tglx@...utronix.de, luto@...nel.org, 
	peterz@...radead.org, keescook@...omium.org, gregory.price@...verge.com, 
	Marco Elver <elver@...gle.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/3] selftests: Fix errno checking in
 syscall_user_dispatch test

On Mon, 3 Mar 2025 at 17:06, Gregory Price <gourry@...rry.net> wrote:
>
> On Mon, Feb 24, 2025 at 09:45:26AM +0100, Dmitry Vyukov wrote:
> >       /* len != 0 */
> > -     prctl(PR_SET_SYSCALL_USER_DISPATCH, op, 0x0, 0xff, 0);
> > +     EXPECT_EQ(-1, prctl(PR_SET_SYSCALL_USER_DISPATCH, op, 0x0, 0xff, 0));
> >       EXPECT_EQ(EINVAL, errno);
>
> This patch should probably just be pulled ahead of everything else,
> since you change the behavior of the syscall, and now you're updating
> the test - but it will fail (since this no longer produces EINVAL).
>
> This patch should probably just be entirely separate, maybe even in
> stable?

Should I do something for this (what)? Or maintainers can pull it?
What tree should pull it?