Re: [PATCH -mm 0/7] execns syscall and user namespace

I haven't had a chance to do a thorough review yet but why is
this needed?

What can be left shared by switching to a new namespace and then
execing an executable?

Is it not possible to ensure what you are trying to ensure with
a good user space executable?


I agree with Eric. In OpenVZ we don't do exec(), because executable itself ensures
correct environment.

Do we need to overcomplicate kernel in this regard?

Thanks,
Kirill

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH -mm 0/7] execns syscall and user namespace
  - From: Cedric Le Goater <[email protected]>

References:
- [PATCH -mm 0/7] execns syscall and user namespace
  - From: Cedric Le Goater <[email protected]>
- Re: [PATCH -mm 0/7] execns syscall and user namespace
  - From: [email protected] (Eric W. Biederman)

Prev by Date: Fix compilation on arm in -rc1-git
Next by Date: Re: Will there be Intel Wireless 3945ABG support?
Previous by thread: Re: [PATCH -mm 0/7] execns syscall and user namespace
Next by thread: Re: [PATCH -mm 0/7] execns syscall and user namespace
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]