Re: [PATCH v2 0/2] fs, close_range: add flag CLOSE_RANGE_CLOEXEC

2020-11-18 Thread Christian Brauner
On Thu, Oct 29, 2020 at 05:47:53PM +0100, Giuseppe Scrivano wrote: > Hi Christian, > > Christian Brauner writes: > > > On Mon, Oct 19, 2020 at 12:26:52PM +0200, Giuseppe Scrivano wrote: > >> When the new flag is used, close_range will set the close-on-exec bit > >> for the file descriptors inste

Re: [PATCH v2 0/2] fs, close_range: add flag CLOSE_RANGE_CLOEXEC

2020-10-29 Thread Giuseppe Scrivano
Hi Christian, Christian Brauner writes: > On Mon, Oct 19, 2020 at 12:26:52PM +0200, Giuseppe Scrivano wrote: >> When the new flag is used, close_range will set the close-on-exec bit >> for the file descriptors instead of close()-ing them. >> >> It is useful for e.g. container runtimes that want

Re: [PATCH v2 0/2] fs, close_range: add flag CLOSE_RANGE_CLOEXEC

2020-10-29 Thread Christian Brauner
On Mon, Oct 19, 2020 at 12:26:52PM +0200, Giuseppe Scrivano wrote: > When the new flag is used, close_range will set the close-on-exec bit > for the file descriptors instead of close()-ing them. > > It is useful for e.g. container runtimes that want to minimize the > number of syscalls used after

[PATCH v2 0/2] fs, close_range: add flag CLOSE_RANGE_CLOEXEC

2020-10-19 Thread Giuseppe Scrivano
When the new flag is used, close_range will set the close-on-exec bit for the file descriptors instead of close()-ing them. It is useful for e.g. container runtimes that want to minimize the number of syscalls used after a seccomp profile is installed but want to keep some fds open until the conta