Date: Fri, 4 Nov 2005 11:51:01 +0000
From: Al Viro <viro@ftp.linux.org.uk>
To: jblunck@suse.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC,PATCH] libfs dcache_readdir() and dcache_dir_lseek() bugfix
Message-ID: <20051104115101.GH7992@ftp.linux.org.uk>
References: <20051104113851.GA4770@hasse.suse.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20051104113851.GA4770@hasse.suse.de>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1072
Lines: 21

On Fri, Nov 04, 2005 at 12:38:51PM +0100, jblunck@suse.de wrote:
> This patch effects all users of libfs' dcache directory implementation.
> 
> Old glibc implementations (e.g. glibc-2.2.5) are lseeking after every call to
> getdents(), subsequent calls to getdents() are starting to read from a wrong
> f_pos, when the directory is modified in between. Therefore not all directory
> entries are returned. IMHO this is a bug and it breaks applications, e.g. "rm
> -fr" on tmpfs.
> 
> SuSV3 only says:
> "If a file is removed from or added to the directory after the most recent
> call to opendir() or rewinddir(), whether a subsequent call to readdir_r()
> returns an entry for that file is unspecified."
 
IOW, the applications in question are broken since they rely on unspecified
behaviour, not provided by old libc versions.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/