From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io1-f47.google.com (mail-io1-f47.google.com [209.85.166.47]) by gnuweeb.org (Postfix) with ESMTPS id E4D077EC44 for ; Sun, 23 Jan 2022 16:36:27 +0000 (UTC) Received: by mail-io1-f47.google.com with SMTP id y84so351405iof.0 for ; Sun, 23 Jan 2022 08:36:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20210112.gappssmtp.com; s=20210112; h=from:to:cc:in-reply-to:references:subject:message-id:date :mime-version:content-transfer-encoding; bh=t2ihpCOT9aaIultqn19S2wUG+GAbHURR2h3vej3cW94=; b=ztHpdqXLKbUiaxeIH0fjcRSyeNmSBOVd+Iy42LMWdBhx2IECF0fz42MSnjhQjM5R1L T4kwmgi7rpwU37dQdhSjhaw0UxqEaAkPwq/uJYfKRxuUzS9KiNp/P9TwBZaWXfW0F0qQ B68XwGrPFNxaRtgDAsJXjrbyVlR3pvjjCwUedw1GptPjBwcGlsLlNlTdNOeSZ40EdrqW 6MNe7eqn+gggrZSFrttxWjs5xnZUKjwWZonnxkDV30e0d0uYZLMzTsHpAdOGkMbPaWdt W1xpUtUBDJukh12wFsSYOTksqCrP7LIu4oWoVejF52e3/2980HyvUnH1fMmyQlKMU/1W 7WSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:in-reply-to:references:subject :message-id:date:mime-version:content-transfer-encoding; bh=t2ihpCOT9aaIultqn19S2wUG+GAbHURR2h3vej3cW94=; b=4QCsq6UPfFLqMF4yc4G/2Avzy76PvAiwywFc2jsHTO5Iks+A/yht+OWJLoB+FhJvMw 3e1aQdOTW1fQkC/OYkB3+hb+gpyO8mHHwhX/zV7hb/ozI99XY3nB8uFFY3Nv61RAdaG3 Ol7BgKgQz5W74N3n9lchWYM0ICkEDJ+Tiy54H1iP1swJ3Zmywrg8yo/X4M0s8AFMufec MRFvbikwVH/E1MIAgJBCgwBm5iy7zIyeVqTFxPB09OuOWXEeHjElJF9RZN4jxHLflQif qy9Yusz2OY9rKn3oykqm47VsNE67JZaEaP13xNyXLJ6ysjbEfgvwwRPaRYFAmphyapSz c98A== X-Gm-Message-State: AOAM533IGhL1Al0kToyL6PtkexxAO70FPyVoZrZG0RmURrVrn9UbP45+ YrV5bpG8IWejwVtnnSUf/SR5rQ== X-Google-Smtp-Source: ABdhPJxDZP1a7NWn+WocNMuiTpLJayZqYXFFEiBnYYzSNqc2LNPKv+G7681AWMhWQR4hL8GUShaamg== X-Received: by 2002:a05:6602:2250:: with SMTP id o16mr1010646ioo.88.1642955786978; Sun, 23 Jan 2022 08:36:26 -0800 (PST) Received: from [192.168.1.116] ([66.219.217.159]) by smtp.gmail.com with ESMTPSA id p5sm4780061iof.50.2022.01.23.08.36.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 23 Jan 2022 08:36:26 -0800 (PST) From: Jens Axboe To: Ammar Faizi Cc: Alviro Iskandar Setiawan , Tea Inside Mailing List , io-uring Mailing List , GNU/Weeb Mailing List , Miyasaki Kohaku In-Reply-To: <20220123074230.3353274-1-ammarfaizi2@gnuweeb.org> References: <20220123074230.3353274-1-ammarfaizi2@gnuweeb.org> Subject: Re: [PATCH] nolibc: Don't use `malloc()` and `free()` as the function name Message-Id: <164295578635.5600.9693251485824219620.b4-ty@kernel.dk> Date: Sun, 23 Jan 2022 09:36:26 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit List-Id: On Sun, 23 Jan 2022 14:42:30 +0700, Ammar Faizi wrote: > Miyasaki reports that liburing with CONFIG_NOLIBC breaks apps that > use libc. The first spotted issue was a realloc() call that results > in an invalid pointer, and then the program exits with SIGABRT. > > The cause is liburing nolibc overrides malloc() and free() from the > libc (especially when we statically link the "liburing.a" to the apps > that use libc). > > [...] Applied, thanks! [1/1] nolibc: Don't use `malloc()` and `free()` as the function name commit: 29ff69397fa13478b5619201347c51159874279e Best regards, -- Jens Axboe