From: Michael Tokarev <mjt@tls.msk.ru>
Subject: unlink(nonexistent): EROFS or ENOENT?
Date: Sun, 29 May 2011 20:08:55 +0400
Message-ID: <4DE26F97.9050607@msgid.tls.msk.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
To: Linux-kernel <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Return-path: <linux-kernel-owner@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

Hello.

Just noticed that at least on ext4, unlinking a
non-existing file from a read-only filesystem
results in EROFS instead of ENOENT.  I'd expect
it return ENOENT - it is more logical, at least
in my opinion.

For one, (readonly) NFS mount returns ENOENT in
this case.

Thanks!

/mjt