From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from esa4.mentor.iphmx.com (esa4.mentor.iphmx.com [68.232.137.252]) by sourceware.org (Postfix) with ESMTPS id 9B4EB3844023 for ; Thu, 17 Jun 2021 20:59:02 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 9B4EB3844023 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=codesourcery.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=mentor.com IronPort-SDR: MOb68owU/CyFgk2s91VnAEJRM+nLEcdZ5QZ4Vtl8tnNIvNclRqd4Fw0u0CduZDOuEl0c77D8Em 4K/AvK2I+K7L+cOQAVloDNRqV/rNR5jrCDk0MuQCGLViECfS+FDeSzNKGtjNHbfQ+fHcMw2VXo v9biKzLuvcB4z8LcTWqg+dCCO1dFbOZQTCq9oy4wP//JGZruqlzyLNgBavQmk4VebbgChXTZct 1wnWHAON+0Rl8a+/fOIJBHgsQjYavnBCl871jcmrl4LlHrxHP1xdSWqIjd+7IytdHZBDwmytYo otA= X-IronPort-AV: E=Sophos;i="5.83,281,1616486400"; d="scan'208";a="62716731" Received: from orw-gwy-01-in.mentorg.com ([192.94.38.165]) by esa4.mentor.iphmx.com with ESMTP; 17 Jun 2021 12:59:01 -0800 IronPort-SDR: ZZFQj7n0gInRhdzbLKv2whe/oFwMf4SKIbshPI4g4xGVCHVo+zOFk5W14nXIDwnYGq0G0TbFO3 ARJvMVOlYEYGI4N0J9JauLhCtukeG6T9GC3DxGZ/jPc9UjQskQtHwkAlG9coFoGmmkpELb+pYy lwQdtKHYdxc7zXWiNMWmdGJUkhVpUAlYEBUQ6ffxLy2WwlA13PQ1D8oYGv3qYszlKOuvwBWpdj T4CwTvRPoedQ7U8m8khTAbD+6FKj11BZWa8mhfxKfoVQ2QrXQft42RzUJoLi/EBafoQfmW2A83 /IM= Date: Thu, 17 Jun 2021 20:58:56 +0000 From: Joseph Myers X-X-Sender: jsm28@digraph.polyomino.org.uk To: Adhemerval Zanella CC: Lukasz Majewski , Subject: Re: [PATCH 00/18] More y2038 fixes In-Reply-To: <188b5674-a34c-5c27-6332-9a549471cf90@linaro.org> Message-ID: References: <20210617115104.1359598-1-adhemerval.zanella@linaro.org> <20210617162021.52a63a3e@ktm> <188b5674-a34c-5c27-6332-9a549471cf90@linaro.org> User-Agent: Alpine 2.22 (DEB 394 2020-01-19) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Originating-IP: [137.202.0.90] X-ClientProxiedBy: svr-ies-mbx-02.mgc.mentorg.com (139.181.222.2) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) X-Spam-Status: No, score=-3120.6 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS, KAM_DMARC_STATUS, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) 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, 17 Jun 2021 20:59:04 -0000 On Thu, 17 Jun 2021, Adhemerval Zanella via Libc-alpha wrote: > > BTW: I'm wondering when the minimal, supported Linux kernel version is > > going to be moved forward? > > We usually follow the minimum LTS supported by Linux kernel developers. However, updates are usually only done when they actually allow significant cleanups in glibc. And given there isn't much benefit on x86_64 to increasing the minimum version, it seems like a good idea to first implement Carlos's proposal to remove the error at glibc startup for an old kernel version number (so people trying to use new glibc in containers on old kernels don't automatically get everything failing at startup, and may well have things work especially if a few syscalls have been backported to the old kernel). Once Carlos's proposal is implemented, a 4.4 minimum *would* allow significant cleanups, such as removing most of the socketcall support. But it would be important to *check* the kernel support in 4.4 for each feature carefully before assuming it to be present globally. (For example, when removing the socketcall support, we can't do so for getpeername or getsockname until the minimum kernel version is 4.20 or later (so not until 2025 based on the current EOL dates at ), because that's when those syscalls were added to the compat syscall table for 32-bit SPARC programs running on 64-bit kernels.) -- Joseph S. Myers joseph@codesourcery.com