From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi1-x22d.google.com (mail-oi1-x22d.google.com [IPv6:2607:f8b0:4864:20::22d]) by sourceware.org (Postfix) with ESMTPS id DA4BE3858437 for ; Thu, 27 Jan 2022 14:17:07 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org DA4BE3858437 Received: by mail-oi1-x22d.google.com with SMTP id s127so6142705oig.2 for ; Thu, 27 Jan 2022 06:17:07 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:from:to:cc:references:in-reply-to :content-transfer-encoding; bh=gsLS7lTXSlEkg9f+bx6euXLXQiGmwhiPVEWOETW/I0s=; b=1NjAgRxbi53HQo8F/wH2oyHav+NhuKfoOXBE2WIDoukS//7zLSoa/w2eAue66svrTU 76sYu6PeRuNhbeeasZW/J/ZOuRvTk8wbEx504QMB7wxMIaENvwzjFMtLmV1LBbg5MTmV kvbhGCrt01rOcjBNLi3FLoU8t9q1cvvEiOcj/yV8txQJy1c+NpVArWhhhlNHiAdPxn3w c2vQ6WshvVUUOoWNkCHGqGotI/nfVwXt+AVfAxd+Hkbiz40Oqh4+tCWaIauFQBHlZwBh r87un/Ec1Fm35xv2JsLO8Ge0wTVrhuF+xfLcEq/n0Kl9l+sykTny8fS+zvBpM423uT7M s/Ww== X-Gm-Message-State: AOAM532RyFOyWsBkfLzIAyQAZG+kN8YZ70hos3lqhFTXIBku6zn6fZQe jqgdAEfHXNGqSOHqllyT7VkrhMHwPHkNgQ== X-Google-Smtp-Source: ABdhPJwRxLR+8ZEllpwfI2B/iYpgOMHbWi40IS8VX9sti1L8UjKJEs8BRY9MY0Yo1RJTCAtzCNEeKg== X-Received: by 2002:a05:6808:f16:: with SMTP id m22mr7219621oiw.141.1643293027301; Thu, 27 Jan 2022 06:17:07 -0800 (PST) Received: from ?IPV6:2804:431:c7cb:27f8:865d:8f66:952e:4ca2? ([2804:431:c7cb:27f8:865d:8f66:952e:4ca2]) by smtp.gmail.com with ESMTPSA id a128sm6968998oob.17.2022.01.27.06.17.06 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 27 Jan 2022 06:17:07 -0800 (PST) Message-ID: Date: Thu, 27 Jan 2022 11:17:05 -0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.1 Subject: Re: [PATCH v4] linux: Fix ancillary 64-bit time timestamp conversion (BZ #28349, BZ #28350) Content-Language: en-US From: Adhemerval Zanella To: Florian Weimer Cc: Adhemerval Zanella via Libc-alpha References: <20211222185239.1088511-1-adhemerval.zanella@linaro.org> <8735lh6vqo.fsf@oldenburg.str.redhat.com> <372ae1ee-0163-7bf4-be1c-cc1f13b1a940@linaro.org> <87bl0149i2.fsf@oldenburg.str.redhat.com> <9263a5c2-48c4-a5d1-c159-2f0ee4e26c52@linaro.org> <87y2352try.fsf@oldenburg.str.redhat.com> <699abc23-7e47-a85f-e553-b5a6c0b1f426@linaro.org> <87h79qql4b.fsf@oldenburg.str.redhat.com> <877dalo0ed.fsf@oldenburg.str.redhat.com> <16fe263b-fc7a-81ba-dd0e-0979f071a409@linaro.org> <87tudpmhih.fsf@oldenburg.str.redhat.com> <80c7253b-8669-c692-ea58-625b3802a4d5@linaro.org> <87pmodmfs2.fsf@oldenburg.str.redhat.com> <6170d1b3-3605-42fc-c01f-1eef59136ad6@linaro.org> In-Reply-To: <6170d1b3-3605-42fc-c01f-1eef59136ad6@linaro.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jan 2022 14:17:09 -0000 On 27/01/2022 11:13, Adhemerval Zanella wrote: > > > On 27/01/2022 11:09, Florian Weimer wrote: >> * Adhemerval Zanella: >> >>> On 27/01/2022 10:32, Florian Weimer wrote: >>>> * Adhemerval Zanella: >>>> >>>>>> Right, I expected something like that, which is why I insisted on adding >>>>>> the time64 symbol aliases. >>>>> >>>>> I can work on a patch for 2.35 if you think this is really required. Another >>>>> options would just to remove the MSG_CTRUNC fro 2.35. >>>> >>>> I really want that fix, but I think we can backport it just after the >>>> release. >>> >>> Right, which fix exactly: the new time64 recvmsg/recvmmsg >> >> The split between time32 and time64 recvmsg/recvmmsg. > > I think then we will need to push it for 2.35. I will prepare a patch. I forgot we already have, although they are are an alias to each other. Meanwhile, the initial fix is ok for 2.35? Do you have any further comment?s