On Wed, Jun 24, 2020 at 01:54:56PM +0200, Christian Brauner
wrote:
> Yep, I already have a fix for this in my tree based on a previous
> report from LTP.
Perfect. (Sorry for the noise then.)
Thanks,
Michal
signature.asc
Description: Digital signature
Hi.
On Tue, May 05, 2020 at 04:04:31PM +0200, Christian Brauner
wrote:
> -SYSCALL_DEFINE2(setns, int, fd, int, nstype)
> +SYSCALL_DEFINE2(setns, int, fd, int, flags)
> [...]
> - file = proc_ns_fget(fd);
> - if (IS_ERR(file))
> - return PTR_ERR(file);
> + int err = 0;
>
On Mi, 24.06.20 09:02, Chris PeBenito (chpeb...@linux.microsoft.com) wrote:
> On 6/23/20 10:57 AM, Lennart Poettering wrote:
> > On Di, 23.06.20 09:41, Chris PeBenito (chpeb...@linux.microsoft.com) wrote:
> >
> > > I've got some challenges using systemd's seccomp support because it
> > >
On 6/23/20 10:57 AM, Lennart Poettering wrote:
On Di, 23.06.20 09:41, Chris PeBenito (chpeb...@linux.microsoft.com) wrote:
I've got some challenges using systemd's seccomp support because it
conflicts with the way my system is managed. I need to manage the seccomp
SystemCallFilter lists in a
Hi,
How to disable seccomp in systemd-nspawn? I'm facing issue while
running fuse-overlayfs and I reported it
https://github.com/containers/fuse-overlayfs/issues/220#issuecomment-648865831
Developer asked me to check if the container is seccomp filtered, as
suspected systemd-nspawn put the
