From mboxrd@z Thu Jan  1 00:00:00 1970
From: "J. R. Okajima" <hooanon05g@gmail.com>
Subject: Re: [PATCH] vfs: get_next_ino(), never inum=0
Date: Wed, 30 Apr 2014 02:42:02 +0900
Message-ID: <18587.1398793322@jrobl>
References: <1398786301-11484-1-git-send-email-hooanon05g@gmail.com>
To: hch@lst.de, dchinner@redhat.com, viro@zeniv.linux.org.uk,
	linux-fsdevel@vger.kernel.org
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from mail05-md.ns.itscom.net ([175.177.155.115]:58838 "EHLO
	mail05-md.ns.itscom.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S932491AbaD2RmF (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Tue, 29 Apr 2014 13:42:05 -0400
In-Reply-To: <1398786301-11484-1-git-send-email-hooanon05g@gmail.com>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>


> There is another unpleasant effect when get_next_ino() wraps
> around. When there is a file whose inum=100 on tmpfs, a new file may get
> inum=100. I am not sure what will happen when the duplicated inums exist
> on tmpfs. ...

Undeterministic behaviour when exporting via NFS?


J. R. Okajima