From: OGAWA Hirofumi Subject: Re: Intentionally corrupted vfat fs causing BUG Date: Mon, 13 Oct 2014 17:35:46 +0900 Message-ID: <87y4sk5pul.fsf@devron.myhome.or.jp> References: <20141010205706.GJ27150@sli.dy.fi> <87h9z97aoh.fsf@devron.myhome.or.jp> <8761fo7667.fsf@devron.myhome.or.jp> <543B8BC7.1040501@nod.at> Mime-Version: 1.0 Content-Type: text/plain Cc: Sami Liedes , linux-fsdevel , Al Viro To: Richard Weinberger Return-path: Received: from mail.parknet.co.jp ([210.171.160.6]:42261 "EHLO mail.parknet.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753173AbaJMIfu (ORCPT ); Mon, 13 Oct 2014 04:35:50 -0400 In-Reply-To: <543B8BC7.1040501@nod.at> (Richard Weinberger's message of "Mon, 13 Oct 2014 10:22:31 +0200") Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Richard Weinberger writes: >> I'm still not sure whether this is right direction or not though, >> because mount operation is root only and untrusted image should run fsck >> before. But, also, Oops is clearly unexpected. Hmmm... > > This limitation is not true anymore. Plug in a USB stick into a recent > Linux desktop, it will automatically mount it... Also think of user > namespaces and FUSE. Not really (well, true, some sort though). It is still controlled by root or capability, right? I.e. still controlled by admin of system. I read user namespaces last time, it doesn't allow to mount the block device by namespace's root. FUSE is allowed to mount by true user (I.e. admin can't disallow it)? I still didn't check it fully. -- OGAWA Hirofumi