From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751497AbVKBFEi (ORCPT ); Wed, 2 Nov 2005 00:04:38 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751498AbVKBFEi (ORCPT ); Wed, 2 Nov 2005 00:04:38 -0500 Received: from relay4.usu.ru ([194.226.235.39]:56283 "EHLO relay4.usu.ru") by vger.kernel.org with ESMTP id S1751497AbVKBFEh (ORCPT ); Wed, 2 Nov 2005 00:04:37 -0500 Message-ID: <4368485C.3050505@linuxfromscratch.org> Date: Wed, 02 Nov 2005 10:02:20 +0500 From: "Alexander E. Patrakov" User-Agent: Debian Thunderbird 1.0.2 (X11/20051002) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Alexander E. Patrakov" Cc: LKML Subject: Re: tmpfs (documentation?) bug References: <436847DD.5050504@ums.usu.ru> In-Reply-To: <436847DD.5050504@ums.usu.ru> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-AntiVirus: checked by AntiVir MailGate (version: 2.0.1.15; AVE: 6.32.0.8; VDF: 6.32.0.132; host: usu2.usu.ru) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Alexander E. Patrakov wrote: > Hello, > > Documentation/filesystems/tmpfs.c currently says: > > If nr_blocks=0 (or size=0), blocks will not be limited in that instance; > if nr_inodes=0, inodes will not be limited. > > However, mounting a tmpfs with "mount -t tmpfs -o size=0 tmpfs > /root/tmpfs" results in a tmpfs where only zero-sized files can live. > So either this behaviour should be fixed to be in accordance with the > documentation, or the documentation should reflect the current behaviour. > Please ignore, that applies to old kernels only, not to 2.6.14. -- Alexander E. Patrakov