Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751694AbdLSSkt (ORCPT ); Tue, 19 Dec 2017 13:40:49 -0500 Received: from mx1.redhat.com ([209.132.183.28]:54966 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750808AbdLSSks (ORCPT ); Tue, 19 Dec 2017 13:40:48 -0500 From: Giuseppe Scrivano To: Al Viro Cc: Andrew Morton , LKML , alexander.deucher@amd.com, broonie@kernel.org, chris@chris-wilson.co.uk, David Miller , deepa.kernel@gmail.com, Greg KH , luc.vanoostenryck@gmail.com, lucien xin , Ingo Molnar , Neil Horman , syzkaller-bugs@googlegroups.com, Vladislav Yasevich Subject: Re: [PATCH linux-next] mqueue: fix IPC namespace use-after-free References: <20171219101440.19736-1-gscrivan@redhat.com> <20171219114819.GQ21978@ZenIV.linux.org.uk> <20171219153225.GA14771@ZenIV.linux.org.uk> <874lomhcwb.fsf@redhat.com> Date: Tue, 19 Dec 2017 19:40:43 +0100 In-Reply-To: <874lomhcwb.fsf@redhat.com> (Giuseppe Scrivano's message of "Tue, 19 Dec 2017 17:59:32 +0100") Message-ID: <87vah2ftn8.fsf@redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Tue, 19 Dec 2017 18:40:48 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 706 Lines: 23 Giuseppe Scrivano writes: > The only issue I've seen with my version is that if I do: > > # unshare -im /bin/sh > # mount -t mqueue mqueue /dev/mqueue > # touch /dev/mqueue/foo > # umount /dev/mqueue > # mount -t mqueue mqueue /dev/mqueue > > then /dev/mqueue/foo doesn't exist at this point. Your patch does not > have this problem and /dev/mqueue/foo is again accessible after the > second mount. although, how much is that of an issue? Is there any other way to delay the cost of kern_mount_data()? Most containers have /dev/mqueue mounted but it is not really going to be used. Would it be possible somehow to postpone it until the first inode is created? Thanks, Giuseppe