From: Florian Weimer <fweimer@redhat.com>
To: Jeff Layton <jlayton@redhat.com>, libc-alpha@sourceware.org
Cc: linux-fsdevel@vger.kernel.org,
Michael Kerrisk <mtk.manpages@gmail.com>,
"Carlos O'Donell" <carlos@redhat.com>,
Yuriy Kolerov <Yuriy.Kolerov@synopsys.com>
Subject: Re: [glibc PATCH] fcntl: put F_OFD_* constants under #ifdef __USE_FILE_OFFSET64
Date: Thu, 18 Aug 2016 08:44:00 -0000 [thread overview]
Message-ID: <560d7245-ab98-2050-d99a-f3ed6d949ea2@redhat.com> (raw)
In-Reply-To: <1471461603.3196.105.camel@redhat.com>
On 08/17/2016 09:20 PM, Jeff Layton wrote:
> It is, but it's preferable to unexpected behavior at runtime. I think
> it's entirely reasonable to require large file offsets in order to use
> OFD locks, but I'm willing to be convinced otherwise if there are use
> cases that you know of that this will break.
I have thought about it some more and I agree that removing the
definitions for !64-bit is a viable course of action.
We should deprecate F_SETLK64 and struct lock64, too, and document that
you should use _FILE_OFFSET_BITS == 64 if you need such locks. That,
and make fcntl type-safe (for both C and C++ with sufficiently recent GCC).
Florian
next prev parent reply other threads:[~2016-08-18 8:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 14:47 Jeff Layton
2016-08-17 15:44 ` Joseph Myers
2016-08-17 17:50 ` Jeff Layton
2016-08-17 17:57 ` Joseph Myers
2016-08-17 18:23 ` Jeff Layton
2016-08-17 16:13 ` Mike Frysinger
2016-08-17 17:34 ` Florian Weimer
2016-08-17 17:40 ` Jeff Layton
2016-08-17 18:02 ` Florian Weimer
2016-08-17 18:21 ` Jeff Layton
2016-08-17 18:51 ` Florian Weimer
2016-08-17 19:20 ` Jeff Layton
2016-08-18 8:44 ` Florian Weimer [this message]
2016-08-18 8:59 ` Andreas Schwab
2016-08-17 20:52 ` Andreas Schwab
2016-08-18 8:45 ` Florian Weimer
2016-08-17 18:43 ` Mike Frysinger
2016-08-17 19:15 ` Jeff Layton
2016-08-17 19:59 ` Michael Kerrisk (man-pages)
2016-08-17 20:05 ` Jeff Layton
2016-08-17 20:37 ` Mike Frysinger
2016-08-17 20:58 ` Jeff Layton
2016-08-17 21:35 ` Mike Frysinger
2016-08-17 21:48 ` Jeff Layton
2016-08-18 9:00 ` Florian Weimer
2016-08-23 11:09 ` Cyril Hrubis
2016-08-23 11:36 ` Jeff Layton
2016-08-23 11:43 ` Cyril Hrubis
2016-08-23 21:11 ` Michael Kerrisk (man-pages)
2016-11-14 13:45 ` Cyril Hrubis
2016-11-22 18:41 ` Florian Weimer
2016-08-18 8:57 ` Florian Weimer
2016-08-17 20:03 ` Mike Frysinger
2016-08-17 21:35 ` Cyril Hrubis
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=560d7245-ab98-2050-d99a-f3ed6d949ea2@redhat.com \
--to=fweimer@redhat.com \
--cc=Yuriy.Kolerov@synopsys.com \
--cc=carlos@redhat.com \
--cc=jlayton@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mtk.manpages@gmail.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).