From: Matthieu Buffet <matthieu@buffet.re>
To: "Mickaël Salaün" <mic@digikod.net>
Cc: "Günther Noack" <gnoack@google.com>,
"Konstantin Meskhidze" <konstantin.meskhidze@huawei.com>,
"Ivanov Mikhail" <ivanov.mikhail1@huawei-partners.com>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Matthieu Buffet" <matthieu@buffet.re>,
"Tahera Fahimi" <fahimitahera@gmail.com>
Subject: [PATCH v3 0/3] samples/landlock: Fix port parsing in sandboxer
Date: Sat, 19 Oct 2024 17:15:31 +0200 [thread overview]
Message-ID: <20241019151534.1400605-1-matthieu@buffet.re> (raw)
Hi Mickaël, Mikhail,
This v3 should have all your comments merged, thank your for your time
reviewing this.
Changes since v2:
- replaced help message with a static format string
- added possible LL_SCOPED values and their effect (also for easier
understanding of expected environment variables, cc: Tahera)
- rebased on mic-linux/next
v2:
Link: https://lore.kernel.org/all/20241003005042.258991-1-matthieu@buffet.re/
Matthieu Buffet (3):
samples/landlock: Fix port parsing in sandboxer
samples/landlock: Refactor help message
samples/landlock: Clarify option parsing behaviour
samples/landlock/sandboxer.c | 112 +++++++++++++++++++++--------------
1 file changed, 69 insertions(+), 43 deletions(-)
base-commit: fe76bd133024aaef12d12a7d58fa3e8d138d3bf3
--
2.39.5
next reply other threads:[~2024-10-19 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-19 15:15 Matthieu Buffet [this message]
2024-10-19 15:15 ` [PATCH v3 1/3] samples/landlock: Fix port parsing in sandboxer Matthieu Buffet
2024-10-22 18:50 ` Mickaël Salaün
2024-10-19 15:15 ` [PATCH v3 2/3] samples/landlock: Refactor help message Matthieu Buffet
2024-10-19 15:15 ` [PATCH v3 3/3] samples/landlock: Clarify option parsing behaviour Matthieu Buffet
2024-10-22 18:50 ` Mickaël Salaün
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=20241019151534.1400605-1-matthieu@buffet.re \
--to=matthieu@buffet.re \
--cc=fahimitahera@gmail.com \
--cc=gnoack@google.com \
--cc=ivanov.mikhail1@huawei-partners.com \
--cc=konstantin.meskhidze@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
/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;
as well as URLs for NNTP newsgroup(s).