Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: "José Pekkarinen" <jose.pekkarinen@unikie.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/7] package/minijail: new package
Date: Wed, 5 Jan 2022 21:41:29 +0100	[thread overview]
Message-ID: <20220105214129.2f5fffae@windsurf> (raw)
In-Reply-To: <20211210141209.1812043-2-jose.pekkarinen@unikie.com>

Hello José,

On Fri, 10 Dec 2021 16:12:04 +0200
José Pekkarinen <jose.pekkarinen@unikie.com> wrote:

> This patch adds a new package for minijail.
> 
> Signed-off-by: José Pekkarinen <jose.pekkarinen@unikie.com>

I wanted to apply after fixing the issues pointed by others, but there
are in fact other issues, which I cannot resolve directly. See below.

> diff --git a/package/minijail/0001-Fix-prlimit-call.patch b/package/minijail/0001-Fix-prlimit-call.patch
> new file mode 100644
> index 0000000000..9f6902ed43
> --- /dev/null
> +++ b/package/minijail/0001-Fix-prlimit-call.patch
> @@ -0,0 +1,29 @@
> +From 09348f06104bf8101a24a0bce235a75a214e1380 Mon Sep 17 00:00:00 2001
> +From: =?UTF-8?q?Jos=C3=A9=20Pekkarinen?= <jose.pekkarinen@unikie.com>
> +Date: Fri, 10 Dec 2021 14:20:30 +0200
> +Subject: [PATCH] Fix prlimit call

What are you "fixing"? You're replacing a prlimit() call by by
setrlimit(), but why? What problem does it solve? Why is it correct to
do that?

> diff --git a/package/minijail/0002-Fix-static-assert.patch b/package/minijail/0002-Fix-static-assert.patch
> new file mode 100644
> index 0000000000..48139e8baa
> --- /dev/null
> +++ b/package/minijail/0002-Fix-static-assert.patch
> @@ -0,0 +1,30 @@
> +From b5d91b793942747e5126e75abca2eebad60ab478 Mon Sep 17 00:00:00 2001
> +From: =?UTF-8?q?Jos=C3=A9=20Pekkarinen?= <jose.pekkarinen@unikie.com>
> +Date: Fri, 10 Dec 2021 14:21:38 +0200
> +Subject: [PATCH] Fix static assert
> +MIME-Version: 1.0
> +Content-Type: text/plain; charset=UTF-8
> +Content-Transfer-Encoding: 8bit
> +
> +Signed-off-by: José Pekkarinen <jose.pekkarinen@unikie.com>
> +---
> + libminijail.c | 3 ---
> + 1 file changed, 3 deletions(-)
> +
> +diff --git a/libminijail.c b/libminijail.c
> +index 45f133e..8323742 100644
> +--- a/libminijail.c
> ++++ b/libminijail.c
> +@@ -2620,9 +2620,6 @@ static int fd_is_open(int fd)
> + 	return fcntl(fd, F_GETFD) != -1 || errno != EBADF;
> + }
> + 
> +-static_assert(FD_SETSIZE >= MAX_PRESERVED_FDS * 2 - 1,
> +-	      "If true, ensure_no_fd_conflict will always find an unused fd.");

You're not fixing the static_assert() here but simply dropping it. Why?
When does it fail? What is the problem with it? Why is it safe to drop
it?

Could you take into account these comments as well as the others
received, and send an update patch?

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-01-05 20:41 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10 14:12 [Buildroot] [PATCH 1/7] package/opensc: new package José Pekkarinen
2021-12-10 14:12 ` [Buildroot] [PATCH 2/7] package/minijail: " José Pekkarinen
2021-12-10 14:48   ` Giulio Benetti
2021-12-10 18:15     ` Arnout Vandecappelle
2021-12-10 20:26       ` Giulio Benetti
2021-12-11  8:30         ` Arnout Vandecappelle
2021-12-11 11:53           ` Giulio Benetti
2021-12-10 19:57   ` Yann E. MORIN
2022-01-05 20:41   ` Thomas Petazzoni [this message]
2022-01-12 14:15     ` José Pekkarinen
2022-01-12 14:51       ` Thomas Petazzoni
2022-01-12 15:08         ` José Pekkarinen
2022-01-12 16:00           ` Thomas Petazzoni
2022-01-13  5:12             ` José Pekkarinen
2021-12-10 14:12 ` [Buildroot] [PATCH 3/7] package/bmx7: " José Pekkarinen
2021-12-10 14:52   ` Giulio Benetti
2021-12-10 20:07   ` Yann E. MORIN
2022-01-05 22:23   ` Thomas Petazzoni
2022-01-10  5:36     ` José Pekkarinen
2021-12-10 14:12 ` [Buildroot] [PATCH 4/7] package/alfred: " José Pekkarinen
2021-12-10 14:54   ` Giulio Benetti
2022-01-05 22:43   ` Thomas Petazzoni
2021-12-10 14:12 ` [Buildroot] [PATCH 5/7] package/aexpect: " José Pekkarinen
2021-12-10 14:56   ` Giulio Benetti
2021-12-10 20:11   ` Yann E. MORIN
2021-12-11  8:43     ` Arnout Vandecappelle
2021-12-11  9:17       ` Yann E. MORIN
2022-01-06  8:40   ` Thomas Petazzoni
2021-12-10 14:12 ` [Buildroot] [PATCH 6/7] package/avocado: " José Pekkarinen
2021-12-10 14:57   ` Giulio Benetti
2022-07-26  8:13   ` Thomas Petazzoni via buildroot
2021-12-10 14:12 ` [Buildroot] [PATCH 7/7] package/avocado-vt: " José Pekkarinen
2021-12-10 15:00   ` Giulio Benetti
2022-07-26  8:21   ` Thomas Petazzoni via buildroot
2022-07-28  6:07     ` José Pekkarinen via buildroot
2021-12-10 14:32 ` [Buildroot] [PATCH 1/7] package/opensc: " Giulio Benetti
2021-12-10 17:34   ` Yann E. MORIN
2021-12-10 14:49 ` Giulio Benetti
2021-12-10 17:06   ` Yann E. MORIN

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220105214129.2f5fffae@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=jose.pekkarinen@unikie.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox