Received: by 10.223.185.116 with SMTP id b49csp7559950wrg; Thu, 1 Mar 2018 07:26:24 -0800 (PST) X-Google-Smtp-Source: AG47ELtegswedxyKHH6mwn3WoJxWo356h4gu1uuukSrmCHNHMNB79BzpgMLLXn3Bbu7OJFJS1uPS X-Received: by 2002:a17:902:5481:: with SMTP id e1-v6mr2265100pli.300.1519917983944; Thu, 01 Mar 2018 07:26:23 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519917983; cv=none; d=google.com; s=arc-20160816; b=1BxDhGLvgHHF3c06gcz3T5BT6kMNtNBoT6CWVkAqmianqydcc1E6n+qLwxX40XvJCC IpL2CcLP7B2HsW0cPFTj/YrsDn7Ud/Gv1J+8i6uGl1H5nGv/uHVv0KO6JzGr1/UaISR2 vxV6YmRWYwcgB0CDhDTwU8B9faj95kAeyV6Ef4dthThAjE1TTrn16INQX+8/a2zckCqB Zwp0pW4oGCdUsPGpwwU7zcpOHRk1oMqhriD5XYFLHZm2TrRMIA9kLOfXZjroKNin9Tr/ Y7XCn21/599bTd2SJVfRDWB9qZTeOlpGYDmB3SaN54rPte5NP7T1m73TQsHgKoaOPeLh n3Ow== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:arc-authentication-results; bh=4P2YwNfQwvS1genGmQVxKih0YIkizzxNvKlX2aZOsKU=; b=xGNUyGWy72taACBpmz7oVq+WERgp6in5yYtPbkJIK0XP6EQxaHLMS79P6rE6EGgIUA oa+T45CmBulVNCAdxKPPXjPILqdUM8i2NVtr/8tvIKlkf3kudxKUdXT/4slNFrkeVm+Z JHe0CGTmLjd6pdAbhf6gl4baG1WZJwecO5YmO5ewv+1X0APExFh5BfjqxG5ccRNT2iPN sg6FJ3/uWNlkc69hFIMz5ve/qzoXPSlI+6ltNAfpBfLoH3ySt9Az0y2Qul1IQCdKVQIr dIPOAE1Rho1c1WwN5CaEuxUgFJMCkVjac+atJU/IHs+Ge/Lp74V+CIOKdgrqM0+vx5i0 Dg8A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=TTgMfd/1; 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 u12-v6si3205807plr.462.2018.03.01.07.26.08; Thu, 01 Mar 2018 07:26:23 -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=pass header.i=@messagingengine.com header.s=fm2 header.b=TTgMfd/1; 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 S1032011AbeCAPYz (ORCPT + 99 others); Thu, 1 Mar 2018 10:24:55 -0500 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:46497 "EHLO out5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1031929AbeCAPYw (ORCPT ); Thu, 1 Mar 2018 10:24:52 -0500 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 320CB20FED; Thu, 1 Mar 2018 10:24:49 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Thu, 01 Mar 2018 10:24:49 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=4P2YwNfQwvS1genGmQVxKih0YIkiz zxNvKlX2aZOsKU=; b=TTgMfd/1QcudFHbE/c1khSJn0gf2OOLcXKN0fWkYD9IDb H4qS9nKOj+divFuuuuB0SfJoADTqfgT6BcwKBlgHp2vOt4F0dvXHTDkAnXhF2SZY rmYNJPJDDFc7MiKQ+JcxA5T/P0Y2qtOu9gBXNIax5VRi/MCMwULyiWbi9g7OihNE XJOBgwaYJjQaJsiNmEyS0+JzpRJP35hhAZSI5sxUA5IjwWvsTpoiTGWm3hHNVqHd VDI0TLVbIApgj4tbSE+rYenZ6dtjKPAkoyXMUjXfzkxK7vCd6UhbPMvxskYtrRTp 3hsQ2l8+l4m24OnCxLIm3iorZ2FQy8vt8v3o1TBrw== X-ME-Sender: Received: from localhost (clnet-b04-243.ikbnet.co.at [83.175.124.243]) by mail.messagingengine.com (Postfix) with ESMTPA id A9A747E321; Thu, 1 Mar 2018 10:24:48 -0500 (EST) Date: Thu, 1 Mar 2018 16:24:50 +0100 From: Greg KH To: Alex Shi Cc: Marc Zyngier , Will Deacon , Ard Biesheuvel , Catalin Marinas , stable@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/29] arm meltdown fix backporting review for lts 4.9 Message-ID: <20180301152450.GA4061@kroah.com> References: <1519790211-16582-1-git-send-email-alex.shi@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1519790211-16582-1-git-send-email-alex.shi@linaro.org> User-Agent: Mutt/1.9.3 (2018-01-21) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 28, 2018 at 11:56:22AM +0800, Alex Shi wrote: > Hi All, > > This backport patchset fixed the meltdown issue, it's original branch: > https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/log/?h=kpti > A few dependency or fixingpatches are also picked up, if they are necessary > and no functional changes. > > The patchset also on repository: > git://git.linaro.org/kernel/linux-linaro-stable.git lts-4.9-spectrevv2 > > No bug found yet from kernelci.org and lkft testing. No bugs is good, but does it actually fix the meltdown problem? What did you test it on? And why are you making this patchset up? What is wrong with the patches in the android-common tree for this? > Any comments are appreciated! You need to start versioning this changeset, as I have no idea if this is the "latest" one or not, right? Or have you not sent out this patchset before? How does this interact with the "spectre" patches? Or am I totally confused here? thanks, greg k-h