[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACaBj2atO=2aAyK+BO5MPS0B3CQNwc98CSHiuy8X2wvkdvJNDQ@mail.gmail.com>
Date: Thu, 27 May 2021 14:45:26 +0200
From: Rodrigo Campos <rodrigo@...volk.io>
To: Kees Cook <keescook@...omium.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Sargun Dhillon <sargun@...gun.me>, containers@...ts.linux.dev,
Tycho Andersen <tycho@...ho.pizza>,
Mauricio Vásquez Bernal <mauricio@...volk.io>,
Giuseppe Scrivano <gscrivan@...hat.com>,
Christian Brauner <christian.brauner@...ntu.com>,
Mickaël Salaün <mic@...ux.microsoft.com>,
Andy Lutomirski <luto@...capital.net>,
Will Drewry <wad@...omium.org>
Subject: Re: [PATCH] selftests/seccomp: More closely track fds being assigned
On Thu, May 27, 2021 at 5:29 AM Kees Cook <keescook@...omium.org> wrote:
>
> Since the open fds might not always start at "4" (especially when
> running under kselftest, etc), start counting from the first assigned
> fd, rather than using the more permissive EXPECT_GE(fd, 0).
>
> Signed-off-by: Kees Cook <keescook@...omium.org>
Nice cleanup, thanks! Just in case, tested it here, works fine. Feel
free to add:
Reviewed-by: Rodrigo Campos <rodrigo@...volk.io>
I can improve the selftest to test the new addfd flag we just added
also in combination existing flags (like setting the fd number to
use), and maybe also split the big chunk test, if you think that is
valuable.
Best,
Rodrigo
Powered by blists - more mailing lists