From: Mark Geisert <mark@maxrnd.com>
To: cygwin-developers@cygwin.com
Subject: Extending domain of O_TMPFILE?
Date: Fri, 5 Feb 2021 02:31:10 -0800 (PST) [thread overview]
Message-ID: <Pine.BSF.4.63.2102050219100.10444@m0.truegem.net> (raw)
Hi folks,
I've been following up on a response I made to a Cygwin user in
https://cygwin.com/pipermail/cygwin/2021-January/247306.html .
I've figured out that Cygwin's implementation of the open() flag O_TMPFILE
follows Linux in that one can't specify the name of a file when using this
flag. User supplies only the path, and Cygwin chooses an obscure file
name for you.
That means the OP's suggested improvement of applying O_TMPFILE semantics
to files created by tmpfile() won't work.
Could we consider expanding the domain of O_TMPFILE so that the user can
supply a name for the temporary file rather than just the path to its
directory? I've been playing around with proof-of-concept code but I want
to make sure this is acceptable before submitting implementation patches.
This would be a Cygwin-specific enhancement to a Linux-specific feature.
I haven't checked yet if the BSDs have O_TMPFILE in any form.
Thanks for any feedback!
..mark
next reply other threads:[~2021-02-05 10:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 10:31 Mark Geisert [this message]
2021-02-05 11:26 ` Corinna Vinschen
2021-02-06 7:56 ` Mark Geisert
2021-02-08 10:34 ` Corinna Vinschen
2021-02-09 10:15 ` Mark Geisert
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=Pine.BSF.4.63.2102050219100.10444@m0.truegem.net \
--to=mark@maxrnd.com \
--cc=cygwin-developers@cygwin.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).