From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mta1.formilux.org (mta1.formilux.org [51.159.59.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9A51723D7D0 for ; Mon, 5 Jan 2026 07:46:51 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=51.159.59.229 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767599213; cv=none; b=AoOlsgc6FsAR6pzzD5TJh9WhYKNOJ2aZUwN6BcQa6YdeHAcf0+A+0/WWHC0YuZPDiCTimsWbU1nIvm7sC/3vR2Er5zE0MyNf53FlZ3ukFk6Hy6w2bp5RSwJqfGTgoGuveDFITKnoxDsAtTSQ7k/gy7p4e0FFcTn/dm4f2RcXPUQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767599213; c=relaxed/simple; bh=Xi6yLqd4HhFYkD5CV6nXpG26m73tTL4bpYbw65c73m0=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Dkgao9nuRLVJqfMeIKTmYFj/BW3xXWA1cY+ZhEk7P6CJw0O2SzIQdZ0pksEWcVmJChARBO3X0Tl5ZJ4y/BmsXoFYfmLJJFc/75EWUAukuAcrqfyq0cDKUTOaWlGTQoAUARSSRrnf4YKjaELlMu7gQo7EIzRFzud8o8vYEEOCNkI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=1wt.eu; spf=pass smtp.mailfrom=1wt.eu; dkim=pass (1024-bit key) header.d=1wt.eu header.i=@1wt.eu header.b=GOCuY7RB; arc=none smtp.client-ip=51.159.59.229 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=1wt.eu Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=1wt.eu Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=1wt.eu header.i=@1wt.eu header.b="GOCuY7RB" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1wt.eu; s=mail; t=1767599209; bh=53eMOI9BqiVNrCR2XCPwyEV3Y5Ef/nc+ZGl8QxGOuPo=; h=From:Message-ID:From; b=GOCuY7RBvKZ3SXEzdP4aEe5PlAmhMeW6gXi71JNaxv/0Q2VQXAhL/8fR8Jsm5KrQy A+Myr8hZZXTFklcIN//SC4CwIgzrAeAzIxjTA+1V83Cy97sfGEZx/5o/gXRF3mnHaG F4L85qAs1wo4c54mQ/KaFu4EyMHzODBAqtG4BlKs= Received: from 1wt.eu (ded1.1wt.eu [163.172.96.212]) by mta1.formilux.org (Postfix) with ESMTP id 88D3AC0943; Mon, 05 Jan 2026 08:46:49 +0100 (CET) Date: Mon, 5 Jan 2026 08:46:49 +0100 From: Willy Tarreau To: Thomas =?iso-8859-1?Q?Wei=DFschuh?= Cc: linux-kernel@vger.kernel.org Subject: Re: [PATCH] tools/nolibc: align sys_vfork() with sys_fork() Message-ID: References: <20260104-nolibc-vfork-v1-1-a63464b9e4e6@weissschuh.net> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20260104-nolibc-vfork-v1-1-a63464b9e4e6@weissschuh.net> On Sun, Jan 04, 2026 at 11:43:13PM +0100, Thomas Weißschuh wrote: > Currently the generic variants of sys_fork() and sys_vfork() differ in > both they precedence of used system calls and the usage of sys_clone() > vs sys_clone3(). While the interface of clone3() in sys_vfork() is more > consistent over different architectures, qemu-user does not support it, > making testing harder. We already handle the different clone() > interfaces for sys_fork() in the architecture-specific headers, and can > do so also for sys_vfork(). In fact SPARC already has such handling and > only s390 is currently missing. > > Signed-off-by: Thomas Weißschuh LGTM. Acked-by: Willy Tarreau thanks, Willy