From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 81668 invoked by alias); 1 Jun 2018 20:50:16 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 81654 invoked by uid 89); 1 Jun 2018 20:50:15 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy= X-HELO: relay1.mentorg.com Date: Fri, 01 Jun 2018 20:50:00 -0000 From: Joseph Myers To: Adhemerval Zanella CC: Florian Weimer , Subject: Re: [PATCH] Fix Linux fcntl OFD locks for non-LFS architectures (BZ#20251) In-Reply-To: Message-ID: References: <1522877210-27934-1-git-send-email-adhemerval.zanella@linaro.org> <36d1d0db-8661-5476-7e42-1a7015f4c766@redhat.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) X-SW-Source: 2018-06/txt/msg00021.txt.bz2 On Fri, 1 Jun 2018, Adhemerval Zanella wrote: > It is not really new, since for architectures with default LFS support this is > transparent and for architectures with non-default LFS my understanding is > functions with *64 suffix are expected to handle cancellation as the non-LFS. *64 functions are generally expected to be analogous with the corresponding non-LFS functions, yes. I think the new fcntl64 API still merits a specific NEWS entry, just like other new function APIs. -- Joseph S. Myers joseph@codesourcery.com