From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Vladimir V. Saveliev" <vs@namesys.com>
Subject: Re: Odd llseek semantics on directories
Date: Mon, 22 Aug 2005 20:19:24 +0400
Message-ID: <4309FB0C.9010409@namesys.com>
References: <1124722904.25421.11.camel@polarbear.fsl.cs.sunysb.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: linux-fsdevel@vger.kernel.org,  reiserfs-list@namesys.com
Return-path: <reiserfs-list-return-25610-reiserfs=m.gmane.org@namesys.com>
list-help: <mailto:reiserfs-list-help@namesys.com>
list-unsubscribe: <mailto:reiserfs-list-unsubscribe@namesys.com>
list-post: <mailto:reiserfs-list@namesys.com>
Errors-To: flx@namesys.com
To: "Charles P. Wright" <cwright@cs.sunysb.edu>
In-Reply-To: <1124722904.25421.11.camel@polarbear.fsl.cs.sunysb.edu>
List-Id: linux-fsdevel.vger.kernel.org

Hello

Charles P. Wright wrote:
> Hello,
> 
> I've noticed that Reiser4's behavior deviates from other file systems
> when seeking with directories.  After reading a directory, if you run
> vfs_lseek(dir, 0, SEEK_CUR), then -ENOENT is returned.   This means that
> you can't pass the identifier back to vfs_lseek with SEEK_SET.
> 
Would you please send your test program?