From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] userns08, CVE-2018-18955: Broken id mappings in nested namespaces
Date: Tue, 27 Jul 2021 12:20:49 +0200 [thread overview]
Message-ID: <YP/eAZixo0oXOJbm@pevik> (raw)
In-Reply-To: <20210727100410.14151-1-rpalethorpe@suse.com>
Hi Richie,
> V2:
> * Formatting of cargs
> * Cleaned up checkpoints
> * Added O_WRONLY to open
Merged, thanks!
Kind regards,
Petr
prev parent reply other threads:[~2021-07-27 10:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 16:22 [LTP] [PATCH] userns08, CVE-2018-18955: Broken id mappings in nested namespaces Richard Palethorpe
2021-07-20 12:35 ` Cyril Hrubis
2021-07-27 10:04 ` [LTP] [PATCH v2] " Richard Palethorpe
2021-07-27 10:20 ` Petr Vorel [this message]
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=YP/eAZixo0oXOJbm@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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