Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp2178377rwl; Thu, 6 Apr 2023 06:58:24 -0700 (PDT) X-Google-Smtp-Source: AKy350Y7KifxLY1l3wu4pxcaSqmKc+hJikdOeTKbJfCV0l1EiBtUknSOhdLKCJ3neqn+ShBYnu+Z X-Received: by 2002:a17:90b:1bc3:b0:237:a174:ce54 with SMTP id oa3-20020a17090b1bc300b00237a174ce54mr11371524pjb.21.1680789504002; Thu, 06 Apr 2023 06:58:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1680789503; cv=none; d=google.com; s=arc-20160816; b=wdkh+6bqQCQ2QmmgCJ3LxH/4VM97lWKT7rDbUhVTZAXCXiHGk/BPzpXetsajNY7c5g r38WrfsR6p8fTQ90lnLPqMyJ8EnArDchTmJ+FaTQCfdttSGhtZuKFb5LbBti28gSq4cL nBZVvdPB0adfgSG+ukiCJBtwLfqwj+qHmUTMU3C65C1MgqayEVlDWAjg5lbrMZxuHgmI oUAamHJwwfFtWlwOgzOD3tbnrGKcIxCgnUlpytIrZbHvwMOU4YmQqWNAH6DCpYoFqeEK sfHPiMdMQ0Ok0l6Au2s1Tc7N+XzXCVrEnWzEl85514G2IcXcvP5ePTW505kRHt9KDae2 K+Dg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature :dkim-signature; bh=JuI7rEXVAd5Io13zAc2gN/AbKEUjXYbUadrLZJs7G7I=; b=GZu6JpINyr8DqBl6g3RnvoQ08f1ssp/mhq+dsxQP+Pc08AeyXc3Sef20Ef29DsfcYt UrZuYps5dHXV2XN4hlDssNXqqgDjgxu6tscfEd7JieDw6HdZ6T0emSijj5pPKjtu6ALi owNWRapF5Kgy1QCIhgWLR/amIseb0JP6J3MYfq3GXY0kx/mciyFhmxrOIv1FaGa0D6ce lXj8PmBzGRDkv+ugCwknTYd9nRDZygsQkGad+eNaneHzxxHi1VfdGDBLA4qzfSo4BSt/ n0EVjfVsOq9Yu5TxTWYSAS/E3+bmgo+pCFPPD04Zlv5eNYO4IEcvBp+OG7QZhtsdshlQ ZKzw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.cz header.s=susede2_rsa header.b=WoQVQrTy; dkim=neutral (no key) header.i=@suse.cz header.b=oQQ8i5x9; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id a8-20020a17090a854800b00233dc8b7c82si3842180pjw.54.2023.04.06.06.58.11; Thu, 06 Apr 2023 06:58:23 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@suse.cz header.s=susede2_rsa header.b=WoQVQrTy; dkim=neutral (no key) header.i=@suse.cz header.b=oQQ8i5x9; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238863AbjDFN5a (ORCPT + 99 others); Thu, 6 Apr 2023 09:57:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37024 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238867AbjDFN51 (ORCPT ); Thu, 6 Apr 2023 09:57:27 -0400 Received: from smtp-out1.suse.de (smtp-out1.suse.de [IPv6:2001:67c:2178:6::1c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 442BB83CE for ; Thu, 6 Apr 2023 06:57:02 -0700 (PDT) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id D6544225FF; Thu, 6 Apr 2023 13:57:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1680789420; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=JuI7rEXVAd5Io13zAc2gN/AbKEUjXYbUadrLZJs7G7I=; b=WoQVQrTyFaKXRHQ6iNlVrkJacxZ6iPuOSlwv8FUO79mXniCR7F9KJ7FZLAnZMg3XfoJo+D TQbwwjFidMIJu2OaeaYCg5kZdTzt/UU17Pe9/xutwnGcSUh84GxYzy8SXx/iJS2OBbTnQ9 tAjLcs8mYcatRmdu3jgboima/pORdq0= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1680789420; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=JuI7rEXVAd5Io13zAc2gN/AbKEUjXYbUadrLZJs7G7I=; b=oQQ8i5x9muTG5IRPWHI/lZ59dWsyEuxxxsZtmpvMsqc+NcJfWSr5ttQUDlnB7X42A/toTH wtozsY0g9vbLWfCA== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id BF57A1351F; Thu, 6 Apr 2023 13:57:00 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id AHP4LazPLmRcGwAAMHmgww (envelope-from ); Thu, 06 Apr 2023 13:57:00 +0000 Date: Thu, 6 Apr 2023 15:58:12 +0200 From: Cyril Hrubis To: Arnd Bergmann Cc: Petr Vorel , Naresh Kamboju , open list , LTP List , llvm@lists.linux.dev, Nathan Chancellor , Anders Roxell , Daniel =?iso-8859-1?Q?D=EDaz?= , Benjamin Copeland , Tudor Cretu Subject: Re: LTP: list of failures on 32bit and compat mode Message-ID: References: <96b67ae8-98dd-40fe-9dde-302e09d12551@app.fastmail.com> <20230406105646.GB1545779@pevik> <7234b8ab-db5c-4f4a-bb9e-ddef9f1a50d3@app.fastmail.com> <20230406124812.GA1589248@pevik> <3c2ba6f9-bea1-4510-8fbb-6521fab74a9d@app.fastmail.com> <20230406131755.GA1608262@pevik> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-1.5 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_SOFTFAIL autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi! > > Thanks! I've just searched in musl as well, because it didn't make sense to me > > it'd be a code for LTP. > > > > "to catch the fault on ltp" I wonder if it's not actually musl bug. > > No, musl is fine here. The problem is that ltp passes an invalid pointer, > expecting to get -EFAULT from the kernel when that faults in > copy_to_user(). > > There is nothing wrong with musl sanitizing the data behind that > pointer, but then you get a signal instead of the EFAULT error. That's actually quite common, usually we fix that by running the test in a child and treating SEGFAULT as a PASS. -- Cyril Hrubis chrubis@suse.cz