Received: by 10.223.185.116 with SMTP id b49csp1045760wrg; Wed, 21 Feb 2018 11:07:47 -0800 (PST) X-Google-Smtp-Source: AH8x227De/PghjJh2cGa3zNQE1Oage6xaMzlkYpRbO5HOYzqbP7q3HS/tkxUXN20j4woLygVYvGa X-Received: by 10.99.113.94 with SMTP id b30mr3519009pgn.228.1519240066953; Wed, 21 Feb 2018 11:07:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519240066; cv=none; d=google.com; s=arc-20160816; b=lpZIjVqzihw/zPGLWZcZ0PseZczMdeF7Eaiv7WRIPzixLJVAECiZFAHFG0lrQK7S+G JXUWYbG1f2zJrdKVOiql4anz1Ml6dZ7OV9+Jl9+yyt1DOEi3zGWxHYvpC+mNjnLWovEq s1cmhnSK9Zm67i6XEultaJDWripTTCQQLYXV0cjgrkIoQ9hL9CxgkNEW/DHf0xGUwPpt lHoKzb0eq1v66TvCBWkKfAH1EQV0WCs50HgpRaNw9DOL8RsIovN7CKtghUQALIVenMOI EdpZGqgyun4kVFSqamO7LdC8A69tNPrSx1fQT7F2QE6XbBs5kWYvUCtBisN8IwDdzELP CfWA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=iRDddS1NJ8/xP9c6jG9+g75D5gu9aUhAWwtbrfgiDz4=; b=HUhcdO2dkX4MJUYreSduANS6bpsFJIwt0IhuPySvKzZ1t7fuGVuPYaZSljTM59uCyG 0z6UiCHy+uTrdxkU4n6M1Pvcvx0jJkhYc8zC+3euFc0hqyOscVJBlvdxqT3/VI4QzP5V 0QG2wbgv2zmmlVQti7VGD+kt6Pmp2hFw0gPVKu40wMitxfY+mghSfk4FR9jepMt5VE5k 4KnSIJmA+XmOQK6uRb5F+iDvgVdPPApvFaZDatHVf1i3ecWtpbhFi/i4hiVYE4uvJHov y8VZCHysMZsqd2fGBgWwoyoOX/LXp6HukjirYaK0UCvyIzdQyyJb/xHUqPAifd5X0oyF qhfQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=ItQVKKpa; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 7-v6si1574154ple.300.2018.02.21.11.07.32; Wed, 21 Feb 2018 11:07:46 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=ItQVKKpa; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S938741AbeBUQ7k (ORCPT + 99 others); Wed, 21 Feb 2018 11:59:40 -0500 Received: from mail-qk0-f196.google.com ([209.85.220.196]:44014 "EHLO mail-qk0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933341AbeBUQ7g (ORCPT ); Wed, 21 Feb 2018 11:59:36 -0500 Received: by mail-qk0-f196.google.com with SMTP id i184so2804478qkf.10 for ; Wed, 21 Feb 2018 08:59:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=iRDddS1NJ8/xP9c6jG9+g75D5gu9aUhAWwtbrfgiDz4=; b=ItQVKKpaPkSrjujcsbi09qZ5CGfphT+GMcadX3rugNHWsYOfYdbg0SYcWBGngFmwLe mx3JldBwUvNVt8rJGKvuHCGxAfLNICoNcmQMEkuNiu0XMh4kZ+QGHtxsKkCaXBBIIvg2 dqr0qvLR+BlimGgneF8M8VyvNgOEAFo4f7KJ3om6SLTJ9UqhZwNjH2J2PICNfCJYTzfT w2Vyl9C4jhHlkZbtruKcc2hlB8Dx8rhTdAh17MWFuZzsLQ+SORZO/VQpcl13q5/BIyTo 1VL2zslIOMFAwIIfwbDAtWwwyQOkdRf3hkZok6U8kL0k0GYu/GX5ko32gNcNISh63QBO 60jQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=iRDddS1NJ8/xP9c6jG9+g75D5gu9aUhAWwtbrfgiDz4=; b=qhXSE34l27HnA3HwUVWm3WIG7ukfOsJRmOMcI8XLLpwu+i+vvSe7HuP2Ag5Lkc1LK3 vZ4BIPEDVuFhJeyS5q94ye7x10fJKbSaEy9rIXylMvgSrS0aFV2F0rVL1kJceTUYk/3H Cp58RbmqW6NjxzR+si7Aft7gIA8HMWHLbga2kS/NZ2LVkPsId3+DdAEyIo6RiNX1EK6b LjPpYrJp/v7bE0ok6fANMgjMOEZC6FfAGLERztZDw4bPLNwvvNHLTVO0kn3wGsZmiUNt 5NJ8nx8n4ZUgKmv1YB7743BjTiOqgQpRfI9DBxkhkMDrMb69v9xeEteKO0EfmINKBV2T PiAw== X-Gm-Message-State: APf1xPDxNyuFv52xV9vNYhmVP9fw2/B9Buzfe3PH6uItWP8VNK3sjgy5 tRgwVs3+v1+uwsxYz3I9s9GZkfXsz9dH3BH+zIk= X-Received: by 10.55.113.69 with SMTP id m66mr1854480qkc.84.1519232375415; Wed, 21 Feb 2018 08:59:35 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.198.17 with HTTP; Wed, 21 Feb 2018 08:59:34 -0800 (PST) In-Reply-To: References: <1518168340-9392-1-git-send-email-joro@8bytes.org> <20180209191112.55zyjf4njum75brd@suse.de> <20180210091543.ynypx4y3koz44g7y@angband.pl> <20180211105909.53bv5q363u7jgrsc@angband.pl> <6FB16384-7597-474E-91A1-1AF09201CEAC@gmail.com> <20180213085429.GB10278@kroah.com> <20180214085425.GA12779@kroah.com> From: Arnd Bergmann Date: Wed, 21 Feb 2018 17:59:34 +0100 X-Google-Sender-Auth: 66rCXRUi6JVvvw23OonjxkbKiKc Message-ID: Subject: Re: [PATCH 00/31 v2] PTI support for x86_32 To: Lorenzo Colitti Cc: Greg KH , Linus Torvalds , Mark D Rustad , Adam Borowski , Joerg Roedel , Andy Lutomirski , Joerg Roedel , Thomas Gleixner , Ingo Molnar , "H . Peter Anvin" , X86 ML , LKML , Linux-MM , Dave Hansen , Josh Poimboeuf , Juergen Gross , Peter Zijlstra , Borislav Petkov , Jiri Kosina , Boris Ostrovsky , Brian Gerst , David Laight , Denys Vlasenko , Eduardo Valentin , Will Deacon , "Liguori, Anthony" , Daniel Gruss , Hugh Dickins , Kees Cook , Andrea Arcangeli , Waiman Long , Pavel Machek , Florian Westphal Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 21, 2018 at 11:26 AM, Lorenzo Colitti wrote: > On Wed, Feb 14, 2018 at 5:54 PM, Greg KH wrote: >> > > IPSEC doesn't work with a 64bit kernel and 32bit userspace right now. >> > > >> > > Back in 2015 someone started to work on that, and properly marked that >> > > the kernel could not handle this with commit 74005991b78a ("xfrm: Do not >> > > parse 32bits compiled xfrm netlink msg on 64bits host") >> > > >> > > This is starting to be hit by some Android systems that are moving >> > > (yeah, slowly) to 4.4 :( >> > >> > Does anybody have test-programs/harnesses for this? >> >> Lorenzo (now on the To: line), is the one that I think is looking into >> this, and should have some sort of test for it. Lorenzo? > > Sorry for the late reply here. The issue is that the xfrm uapi structs > don't specify padding at the end, so they're a different size on > 32-bit and 64-bit archs. This by itself would be fine, as the kernel > could just ignore the (lack of) padding. But some of these structs > contain others (e.g., xfrm_userspi_info contains xfrm_usersa_info), > and in that case the whole layout after the contained struct is > different. So this is x86 specific then and it already works correctly on all other architectures (especially arm64 Android), right? Arnd