linux-kernel - Re: UBIFS seekdir()/telldir() issue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 30 May 2008 13:57:45 +0300
From:	Adrian Hunter <ext-adrian.hunter@...ia.com>
To:	Jan Kara <jack@...e.cz>
CC:	Artem Bityutskiy <Artem.Bityutskiy@...ia.com>,
	Christoph Hellwig <hch@...radead.org>,
	David Woodhouse <dwmw2@...radead.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: UBIFS seekdir()/telldir() issue

Jan Kara wrote:
>   The sequence you write above is actually incorrect I think. Noone
> guarantees that the cookie returned by telldir() is valid after
> closedir(). What is a bigger (and quite common) problem is, if somebody
> uses readdir/telldir/seekdir while someone else creates/deletes files in
> the directory. The standard implies in this case that subsequent
> readdir should return all the files which were not touched (or all files
> after position set by seekdir if used...).

Not according to this:

http://www.opengroup.org/onlinepubs/009695399/functions/readdir.html

	"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() returns an entry for that file
	is unspecified."


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/