| 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
| ||
|
Message-ID: <2c0942db0807290935s67eba63te5bb826a0ab7c752@mail.gmail.com> Date: Tue, 29 Jul 2008 09:35:32 -0700 From: "Ray Lee" <ray-lk@...rabbit.org> To: "Jeremy Fitzhardinge" <jeremy@...p.org> Cc: Oliver.Soltys@...l.renesas.com, linux-kernel@...r.kernel.org Subject: Re: directory sort order no longer beginning with "." and ".."? On Tue, Jul 29, 2008 at 7:53 AM, Jeremy Fitzhardinge <jeremy@...p.org> wrote: > Oliver Soltys wrote: >> >> My question: is this a bug, or a feature? I could not find anything about >> that >> anywhere... >> >> Does anybody have an idea, how I can fix this? Unfortunately, our >> application >> can not be changed. > > No Unix-like system makes any guarantee about the order of '.' and '..' with > respect to other directory entries. They've often appeared first as an > implementation side-effect, but that's highly system and filesystem > dependent. > > If you can't modify the app, you might consider some LD_PRELOAD library to > replace readdir with something that sorts the results in the order your app > expects. There's already examples of that kind of thing to sort the results > by inode. That's a good idea, though based on his description it's even easier. The LD_PRELOAD just needs to artificially introduce . and .., at the beginning and toss them out once it hits them in the list. No sorting required. -- 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/
Powered by blists - more mailing lists