From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E0688EB64D8 for ; Thu, 22 Jun 2023 17:20:47 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230494AbjFVRUq (ORCPT ); Thu, 22 Jun 2023 13:20:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52974 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230404AbjFVRUi (ORCPT ); Thu, 22 Jun 2023 13:20:38 -0400 Received: from gnuweeb.org (gnuweeb.org [51.81.211.47]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 555FF19A9; Thu, 22 Jun 2023 10:20:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gnuweeb.org; s=default; t=1687454436; bh=kqY+PXK/BHeCUujDvP0OTwyGNYeTRsgl8KnpZQ6sEx0=; h=From:To:Cc:Subject:Date; b=nRRA0/7QC0abjoTuDRJ3wJvKcqpQqPpJLhfTPZyGR93TzsXFmQgRB8+H/IEiwlYGa nGjWIpSoAnvynqkwqNO0ZrlXPYQb+TSBftuBGQlYe/dCKev8yv8uV/CWzWeNlKen89 22JbFidcg7W/z0lBZGKFlPv0t9gl+6eg5U/dQmgoEKaQWwg9OK+ZrtNLvDVZa05e6l vIgIck4ZXGjLHTTAUXFEb0Mm8gVzqG40dyYvk2BgwU0F04aw4ep+Gg0jg/GQu9OjKH GheqIu4tYckPUphce4DHErsP6rthZW5NS0pSouXZSP+RKgZen/g7iqhAWyXj34CIVL wvPGt1o0j4R4w== Received: from integral2.. (unknown [68.183.184.174]) by gnuweeb.org (Postfix) with ESMTPSA id 44E9C249D74; Fri, 23 Jun 2023 00:20:33 +0700 (WIB) From: Ammar Faizi To: Jens Axboe Cc: Alviro Iskandar Setiawan , Guillem Jover , Jeff Moyer , Stefan Hajnoczi , Michael William Jonathan , Matthew Patrick , io-uring Mailing List , Linux Kernel Mailing List , GNU/Weeb Mailing List Subject: [RFC PATCH liburing v1 0/3] Introduce '--use-libc' option Date: Fri, 23 Jun 2023 00:20:26 +0700 Message-Id: <20230622172029.726710-1-ammarfaizi2@gnuweeb.org> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: io-uring@vger.kernel.org Hi Jens, Hi Stefan and Guillem, This is an RFC patch series to introduce the '--use-libc' option to the configure script. Currently, when compiling liburing on x86, x86-64, and aarch64 architectures, the resulting binary lacks the linkage with the standard C library (libc). To address the concerns raised by Linux distribution package maintainers regarding security, it is necessary to enable the linkage of libc to liburing. Especially right now, when the security of io_uring is being scrutinized. By incorporating the '--use-libc' option, developers can now enhance the overall hardening of liburing by utilizing compiler features such as the stack protector and address sanitizer. See the following links for viewing the discussion: Link: https://security.googleblog.com/2023/06/learnings-from-kctf-vrps-42-linux.html Link: https://lore.kernel.org/io-uring/20230621100447.GD2667602@fedora Link: https://lore.kernel.org/io-uring/ZJLkXC7QffsoCnpu@thunder.hadrons.org There are three patches in this series. - The first patch removes the '--nolibc' option from the configure script as it is no longer needed. The default build on x86, x86-64, and aarch64 architectures is still not using libc. - The second patch introduces the '--use-libc' option to the configure script. This option enables the linkage of libc to liburing. - The third patch allows the use of the stack protector when building liburing with libc. Please review. Thank you. Signed-off-by: Alviro Iskandar Setiawan Signed-off-by: Ammar Faizi --- Ammar Faizi (3): configure: Remove --nolibc option configure: Introduce '--use-libc' option src/Makefile: Allow using stack protector with libc configure | 40 +++++++++++++++------------------------- src/Makefile | 7 +++---- 2 files changed, 18 insertions(+), 29 deletions(-) base-commit: 49fa118c58422bad38cb96fea0f10af60691baa9 -- Ammar Faizi