Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp525113pxk; Thu, 17 Sep 2020 09:06:50 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzjRghiVelZ7Gfa9nEdQ4R/5xa80eeCrvcx5JwXwPQlwDGydJ4YH14YhZz3+FaeHDsM+QkP X-Received: by 2002:a05:6402:503:: with SMTP id m3mr34179441edv.45.1600358810359; Thu, 17 Sep 2020 09:06:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1600358810; cv=none; d=google.com; s=arc-20160816; b=nPWuBWE5mg/Vi2HxJ1jjJlrMjStIUHMDLpSl0X1HGE680wOPFLEA+SgD5yVPSrVK8+ 84a0Gwg/1G9zBZ52J9hLZF+FGxpQ/IZ/+uKKQW0RilqwL2YJ3GkXlS7I1mSObli9Uilm Up9vYBsf3GGKUf9vNrC/quh53JT/dOVUNTCfMmGpq3+p1EgHjZLSTNL/Fb3iUK23f/pR HU1XRaQiy2rKCUfQ+i/G+iz/P7JHId+vO3uBJQ44c8Q3yC5D0eSrZT/2GQIOWbg+voKL VEsNWWP02dforwLIrrTo93GziXp2YBTFHGV7mFWP07/9wz7J4G1L1IgJYVMsB1eW6hEY X+Mw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:in-reply-to:date :references:subject:cc:to:from; bh=yf4sAlR3lFa4RSYlU7aP0MCQZYapAoBZn8d6vNDeKK8=; b=i17PVXgRqZ9MFAVUB+9SUjFXpzB978N77uaxGEXmamkriP6DJO/bMpuuvVb8OpgR7B Ekge1XRapCWc3LYrCgu9u9iiyk0CLI557R+As7L/6S3yg3EWDlN9MXYJ8wblSYsBlku9 RAyke7yzO3hye8LCvNBBLYi3nxypC9uNF8bCQXQdSgpZwsv5aZUQxYcr3JBOygwpoQ0R Ih+p4XGAzSryHzeUPHnwLZGRldGsZD6cqVAYtTvOaeF3w0XWCs/N8WpXl0OjN6b7f5Bd uVjV5kfEaNFmVm+wj36Wyhpo4yxQ502iDH/61j3j/9FmT8Lcy37FfplIsqhe+8cwSP0P Nlaw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id q24si230458eju.323.2020.09.17.09.06.24; Thu, 17 Sep 2020 09:06:50 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728297AbgIQQFJ (ORCPT + 99 others); Thu, 17 Sep 2020 12:05:09 -0400 Received: from albireo.enyo.de ([37.24.231.21]:53170 "EHLO albireo.enyo.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728269AbgIQQDH (ORCPT ); Thu, 17 Sep 2020 12:03:07 -0400 Received: from [172.17.203.2] (helo=deneb.enyo.de) by albireo.enyo.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1kIwLq-0001jb-Tk; Thu, 17 Sep 2020 16:01:38 +0000 Received: from fw by deneb.enyo.de with local (Exim 4.92) (envelope-from ) id 1kIwLq-0006JJ-P8; Thu, 17 Sep 2020 18:01:38 +0200 From: Florian Weimer To: "Madhavan T. Venkataraman" Cc: kernel-hardening@lists.openwall.com, linux-api@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-fsdevel@vger.kernel.org, linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, oleg@redhat.com, x86@kernel.org, libffi-discuss@sourceware.org Subject: Re: [PATCH v2 0/4] [RFC] Implement Trampoline File Descriptor References: <20200916150826.5990-1-madvenka@linux.microsoft.com> <87v9gdz01h.fsf@mid.deneb.enyo.de> <96ea02df-4154-5888-1669-f3beeed60b33@linux.microsoft.com> Date: Thu, 17 Sep 2020 18:01:38 +0200 In-Reply-To: (Madhavan T. Venkataraman's message of "Thu, 17 Sep 2020 10:57:20 -0500") Message-ID: <87y2l8xuhp.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Madhavan T. Venkataraman: > On 9/17/20 10:36 AM, Madhavan T. Venkataraman wrote: >>>> libffi >>>> ====== >>>> >>>> I have implemented my solution for libffi and provided the changes for >>>> X86 and ARM, 32-bit and 64-bit. Here is the reference patch: >>>> >>>> http://linux.microsoft.com/~madvenka/libffi/libffi.v2.txt >>> The URL does not appear to work, I get a 403 error. >> I apologize for that. That site is supposed to be accessible publicly. >> I will contact the administrator and get this resolved. >> >> Sorry for the annoyance. > Could you try the link again and confirm that you can access it? > Again, sorry for the trouble. Yes, it works now. Thanks for having it fixed.