From: Dmitry Selyutin <ghostman.sd@gmail.com>
To: musl@lists.openwall.com
Subject: Re: readdir(3): behavior on descriptors with O_SEARCH
Date: Sun, 28 Aug 2016 20:14:31 +0300 [thread overview]
Message-ID: <CAMqzjes-LQe9MYH4ZHEyv_t6pd0jY-AcoeGsghwcVs=y30NhsQ@mail.gmail.com> (raw)
In-Reply-To: <20160828162037.GG15995@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 133 bytes --]
I think I got the idea; now I understand that the reported behavior is not
a bug. Thank you very much for explanations and patience!
[-- Attachment #2: Type: text/html, Size: 150 bytes --]
prev parent reply other threads:[~2016-08-28 17:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMqzjetOkwQ7wi4p3MY_HT46v6pVRh_eHSi6SbwC96qoz+ivFg@mail.gmail.com>
2016-08-27 18:23 ` Dmitry Selyutin
2016-08-28 7:10 ` Markus Wichmann
2016-08-28 8:12 ` Dmitry Selyutin
2016-08-28 9:02 ` Dmitry Selyutin
2016-08-28 15:06 ` Rich Felker
2016-08-28 16:02 ` Dmitry Selyutin
2016-08-28 16:20 ` Rich Felker
2016-08-28 17:14 ` Dmitry Selyutin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMqzjes-LQe9MYH4ZHEyv_t6pd0jY-AcoeGsghwcVs=y30NhsQ@mail.gmail.com' \
--to=ghostman.sd@gmail.com \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).