From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tokarev Subject: 2.6.35: unshare(NEWNS) does not work inside a container anymore? Date: Tue, 31 Aug 2010 15:02:15 +0400 Message-ID: <4C7CE137.5090009@msgid.tls.msk.ru> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org List-Id: containers.vger.kernel.org I just noticed a regression - immediately after updating kernel from 2.6.32 to 2.6.35 (I skipped .33 and .34). Namely, unshare(CLONE_NEWNS) stopped workin from within a container, like this: unshare(CLONE_NEWNS) = -1 EINVAL (Invalid argument) There's no other fancy stuff going on around, just plain unshare and exec a new shell. What's wrong with 2.6.35 in this context? Thanks. /mjt