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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id C41BDC433F5 for ; Fri, 6 May 2022 17:32:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=KiRTaoU+1ygTldVUhRuBLskCYOrMuN+/SVgVyDECBfY=; b=u0d8DFp708iPbE DVlVtDoponjXUzG68r+49UQgJlilNCplNp3E5+UXzmNm7sw6CBNk8ZSlMSe1PHj/mEruJM06AeMcv tyHKEuftKkYvyeeFPQQIauAhTwZk53W0uPxO4qK9I9ccRHp4FuHj3fzFi5q2L4P57PDsn6hh8hn33 67ZuNmo9QkVi0aORvqdZTuKXn37Wz8X9tvgBcQI7bJCMFEi4wzJkT5xPO9JqoHwvBPAKOKBjY67Ha rhHKvKQw/SislMS3vNuisohvK6HbKuDkb7/geQWvIJOBGO5OZkxaJG6KNWrNZhiE3rpYtjJ7mh3zJ 0EK/LWlaHkR8cWNMMnLg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nn1nu-004WzT-Lj; Fri, 06 May 2022 17:31:46 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nn1ns-004Wyf-4m for linux-arm-kernel@lists.infradead.org; Fri, 06 May 2022 17:31:45 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 4A985620C0; Fri, 6 May 2022 17:31:43 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 1B3C9C385AC; Fri, 6 May 2022 17:31:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1651858302; bh=XM4Gk5T8GH7GMEQf6U7SdCZ/bJ3i7FcXCA8a6u/+Phw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=uuEgS8uT/cx0rVZpl3sJSdC+aa46jfK7MQTmuUq1/7k/Q1utE92cfKe2AwGDY4Szm zqucEQ9F4R+MHnozBuS4/elW/i5mKokD5lKRwYCRpx+Pa6HXThFwzqoWdApxm1HsX9 ODHxvi5F7XaFwBO5T64FGZTtnOWHhNGzQ/wbffhcqHRORum3xp1cvXJqRUyGQXm81F rXChqOeKXsj0KYO38Bi7qpGWDKvTg5nSi19tvRpYc2rYYqR7ROT3ZwxU3IPtFK8EbC k1Nex2dBChoxmrlm4S/SIaSepRjZqL/Yv4T1Fc/0CroYXjyRrbedY4OFjB8sCb0g45 brfTNsHvA284A== Date: Fri, 6 May 2022 10:31:40 -0700 From: Josh Poimboeuf To: Mark Rutland Cc: Peter Zijlstra , Chen Zhongjin , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-arch@vger.kernel.org, jthierry@redhat.com, catalin.marinas@arm.com, will@kernel.org, masahiroy@kernel.org, jpoimboe@redhat.com, ycote@redhat.com, herbert@gondor.apana.org.au, davem@davemloft.net, ardb@kernel.org, maz@kernel.org, tglx@linutronix.de, luc.vanoostenryck@gmail.com Subject: Re: [RFC PATCH v4 22/37] arm64: kernel: Skip validation of kuser32.o Message-ID: <20220506173140.gkuhf3kzxq7mxfi2@treble> References: <20220429094355.122389-1-chenzhongjin@huawei.com> <20220429094355.122389-23-chenzhongjin@huawei.com> <20220505092448.GE2501@worktop.programming.kicks-ass.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220506_103144_247311_2FDF79C2 X-CRM114-Status: GOOD ( 11.07 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, May 05, 2022 at 11:56:45AM +0100, Mark Rutland wrote: > The objects under arch/arm64/kernel/{vdso,vdso32}/ are all userspace objects, > and from userspace's PoV the existing secrtions within those objects are > correct, so I don't think those should change. > > How does x86 deal with its vdso objects? On x86, we just use OBJECT_FILES_NON_STANDARD (like the up-thread patch) to tell objtool to ignore all the vdso objects. That should be fine for vdso, since it doesn't actually end up as text in vmlinux. -- Josh _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel