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 18968C47087 for ; Wed, 9 Mar 2022 16:50:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238480AbiCIQvF (ORCPT ); Wed, 9 Mar 2022 11:51:05 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35128 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235886AbiCIQez (ORCPT ); Wed, 9 Mar 2022 11:34:55 -0500 Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B5B35AC065 for ; Wed, 9 Mar 2022 08:30:18 -0800 (PST) Received: by mail-pf1-x432.google.com with SMTP id s11so2738128pfu.13 for ; Wed, 09 Mar 2022 08:30:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=OEKJ6HDfRbAYXq1y3GQ16S8ECnj8rGvJ1M6VsKHeWho=; b=oIHRdIQt5LoDmfPbY/G+bBH9o203m/KAHGz2i3DiFvY04vAFtOZbiV2VNw1Bco6aPR 7KbjGoeqlwQ3COOJKgMqcvt6n0uAgO8pXJ9sECo3BMw6jNYxt57ENxj/F5kjvVMnCAXv jY2cx0MvlUyBrD5/D8cKaWx8Xmj0/ViDCRVWQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=OEKJ6HDfRbAYXq1y3GQ16S8ECnj8rGvJ1M6VsKHeWho=; b=Vl4bEM4f/mkLUqjDzl/UyRkQD7cDDaFkuTFtbMKIXAVBo7djmZSfcK60CFAVWJo8Te SMrSo39yrOI/HD7g+5P7Q3tVdosHghKXQYo6R7Zt6xVOUpJD4Oe91yHZlnes6RDjGL4y OUsAizSCOXR9vL9kOT4uLq2+EBxKu3nSLfkVC+bxqyWrk9Rn71PwDbO7EgLlfLLM4NOi YDy2zAtRul5tnOaENaz7eFlOpxuDcOfqrsOMKS1R6BnGCjForzzP6p97gwUJRcKR8ebl xUkRqWndFAFU5Yid76tzKzB/ZEGAE15tBsaNDEyxSDOPd8mew3JPa5kG/BH2wr0+qWK/ bKkw== X-Gm-Message-State: AOAM5317THoSZttNoCQFONKVNvSyHSclSlnpaYOTDvaocbhSaK9EH1oq 3jPGxj2IGoClrV2KxIUkIfZlbA== X-Google-Smtp-Source: ABdhPJysLOSUH1ejLQlt60xHSX+d3Bmy5LiPEBTc5BsVYUZY79bDZ5hXlYyKJbRu0bUDKCQC8AewHg== X-Received: by 2002:a05:6a00:140b:b0:4e1:2cbd:30ba with SMTP id l11-20020a056a00140b00b004e12cbd30bamr340497pfu.46.1646843418232; Wed, 09 Mar 2022 08:30:18 -0800 (PST) Received: from www.outflux.net (smtp.outflux.net. [198.145.64.163]) by smtp.gmail.com with ESMTPSA id g28-20020a63111c000000b00374646abc42sm2841805pgl.36.2022.03.09.08.30.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 09 Mar 2022 08:30:17 -0800 (PST) Date: Wed, 9 Mar 2022 08:30:17 -0800 From: Kees Cook To: Michael Ellerman Cc: Michael Ellerman , Greg Kroah-Hartman , Andrew Morton , Helge Deller , Christophe Leroy , Paul Mackerras , Benjamin Herrenschmidt , "James E.J. Bottomley" , Arnd Bergmann , linuxppc-dev@lists.ozlabs.org, linux-parisc@vger.kernel.org, linux-arch@vger.kernel.org, linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH v4 00/13] Fix LKDTM for PPC64/IA64/PARISC v4 Message-ID: <202203090829.53A243306@keescook> References: <164674125384.3322453.12551849351633372798.b4-ty@ellerman.id.au> <87r17bnbxx.fsf@mpe.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87r17bnbxx.fsf@mpe.ellerman.id.au> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 09, 2022 at 12:37:14PM +1100, Michael Ellerman wrote: > Michael Ellerman writes: > > On Tue, 15 Feb 2022 13:40:55 +0100, Christophe Leroy wrote: > >> PPC64/IA64/PARISC have function descriptors. LKDTM doesn't work > >> on those three architectures because LKDTM messes up function > >> descriptors with functions. > >> > >> This series does some cleanup in the three architectures and > >> refactors function descriptors so that it can then easily use it > >> in a generic way in LKDTM. > >> > >> [...] > > > > Applied to powerpc/next. > > I also have it in an rc2-based topic branch if there are any merge > conflicts that people want to resolve, I don't see any in linux-next at > the moment though. > > https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/log/?h=topic/func-desc-lkdtm Thanks! I've got some core changes coming for lkdtm, but I'm waiting until after the merge window to rebase them and get them into -next. -- Kees Cook