From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.1 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 24170 invoked from network); 10 May 2021 05:51:11 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 10 May 2021 05:51:11 -0000 Received: (qmail 5667 invoked by uid 550); 10 May 2021 05:51:08 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 5633 invoked from network); 10 May 2021 05:51:07 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Ug2fMepVr4oDIdbaV9ld1c1waw7JT/+lhgd4EOxpLoc=; b=QDllrpVwk7fAeCzvj9n/0Bn19s5aVGZLZhsQ4JI3RAo1OmaJ62oxOnXW22dOyy761d ELgwz8HlPH2VZby473B/0NGg0nU3FTvmWGmmWGDE4nv5zWn+h7BIRlYtkBj9YhF6uT0u UWgfSntt6ocbxWdEL6324Xlr+HXGOVVAfRw4DNc3ALXmRx7KLPxGlDm70rfuuL8IOh8j FWFOR7FKN9eQchQy9gAWfRPqdkvVI1P9rS4Gk2rIlZxImxgm1rdfaOsNLdVVzav4hf+D UDr/w2lIQW/1raaKybb4IgdPWhj3OJvcXmEe6uan5BAbndWMusnj2aw07l9d8BCurkAF TyeA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Ug2fMepVr4oDIdbaV9ld1c1waw7JT/+lhgd4EOxpLoc=; b=FpSbE4reWkCPbLBe+fTKhThdsAhpyP895GMMPSGD8tsjq5cvM4rlOCuLc4wRcTQGvE 48pqkxSFYV6u6XU8XoewLdvRS4kU9jPU19JQMe748UFysOr2opnxyyoUPtHkqRqBhAa2 QaDjmANc++5OdDnKPyNWuYCMXiaFUE5Nnxxo/K/EruZi5vfcKFJdhnZJ4RUzYib2Vxuk hojhzIuF3+MEK/tq8LdFEPFveqKx2mhz50puoOCY3U5Es3rs1TPqYQiwFWXWwIlvbCZT lEoizPxW0wdiRUVdV8M5hPAO+TSoDizrsda14+s6Vrw0jHU46VxX2v1ODkEZELbHwLq9 7GEg== X-Gm-Message-State: AOAM532lJ8ZrkZQMupKlyVUQBiOZkHXvTLYcTrNfZxQIF4E4m749mVkg m7/WTZ3WpHy5pE2PnnJ78CTBiOZkB6SP6T+sxOb1aZX6 X-Google-Smtp-Source: ABdhPJwi5yLydCJ/Us6Nu8urPSNlsPRqo+mi7nn3TGwewTf+d3S5HkkpQIdEA/F4Ep91O94RQKJBK5z5ftcGCSYOg/4= X-Received: by 2002:a05:6512:3d2:: with SMTP id w18mr15605208lfp.573.1620625856267; Sun, 09 May 2021 22:50:56 -0700 (PDT) MIME-Version: 1.0 From: Martin Vajnar Date: Mon, 10 May 2021 07:50:44 +0200 Message-ID: To: musl@lists.openwall.com Content-Type: multipart/alternative; boundary="0000000000007a0a2105c1f35cae" Subject: [musl] Backwards kernel compatibility --0000000000007a0a2105c1f35cae Content-Type: text/plain; charset="UTF-8" Hello guys, I'd like to ask, if it is generally supported to run recent musl on older kernels? My primary concern is that there are new syscalls being added to linux, while at the same time I do not see a switch similar to glibc's to select compatibility mode (--enable-kernel). Is there some means which prevent invocation of unimplemented syscalls on older kernels when using musl? Best regards, Martin Vajnar --0000000000007a0a2105c1f35cae Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello guys,

I'd like to ask, if it is generally supported to run recent musl on ol= der kernels? My primary concern is that there are new syscalls being added = to linux, while at the same time I do not see a switch similar to glibc'= ;s to select compatibility mode (--enable-kernel). Is there some means whic= h prevent invocation of unimplemented syscalls on older kernels when using = musl?

Best regards,
Martin Vajnar
--0000000000007a0a2105c1f35cae--