Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp531891ybl; Sat, 18 Jan 2020 05:38:39 -0800 (PST) X-Google-Smtp-Source: APXvYqwYIBHWWssX6z6mNeix94DHb7SR0uQjX+LvhM+qV3xJEtxPCBKqvyGMwiCe69KzdTAWyH3k X-Received: by 2002:a9d:518b:: with SMTP id y11mr9365784otg.349.1579354718978; Sat, 18 Jan 2020 05:38:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1579354718; cv=none; d=google.com; s=arc-20160816; b=AotM2qwpFQQ0cJxAxvde8xevsu/2kFwE/RHPutQvAOB9rM0HYU5ksPtoPT80djeoTQ 9qQMoCBY1w59md6tTqBobi33npI4jmE0ts3bo9b9VUD9a+oXInGTlKleptpD1rJYHqoA 6fg9C0h6/ILqdvP6FAhYMzDiYnaWB2LHEFTgI4mEBkXYOFND45pCyfYAqRlRYKBZPyu7 lLyLirwlMMAiY3z7KsgcgGcJHx2QFRnF5H+bdMs4+ca9BxzfKdJm3vtJA5pFXqys8fc6 Z7t/QnERhLAvV0H9P0UHaYPK/OjeZblwqf24RexeShhdBRtBCLU8XtbH3KRpa7Sa8mxK +suQ== 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 :in-reply-to:references:mime-version:dkim-signature; bh=VF7Ybre9nicDdkbJ8YLCx9ZGXACXxQfpsesRhP5xc4k=; b=pMPtxqTdWLLpDCRw8zi6EdNCPbZfZTEFyYqcGVVT5mQNpiLtSK1wpvyyNoM0XVxlLZ nNivgAEZbAj6BHtaOyAmaRj+TGCQHvfH+LhHyVz2++wz9MpjdZOfM6O9JnrrHq4bQS9p ks0MKlGIl19Z0bhacw3cmPtZ6Ax1xb9r/0VK1BnVe+ZIzRjTN1dthf7g6C9JULJrTTKy Ah7Ik3JR+36tRBtpyVU6cyalWWP4faMnXx44v1zZ5/SpyzbPEhVBfRdH+FaUBzgIcqfm KJjnJkjoItue0/aeRP3iaRHVH7uQzfLeJ85ftlmf5tPRgUMp0jMyEpBzXPJhWXxZrIpb Botg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=EY3A6DSL; 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; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n1si14778423oic.225.2020.01.18.05.38.27; Sat, 18 Jan 2020 05:38:38 -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=@google.com header.s=20161025 header.b=EY3A6DSL; 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; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728949AbgARNha (ORCPT + 99 others); Sat, 18 Jan 2020 08:37:30 -0500 Received: from mail-qv1-f66.google.com ([209.85.219.66]:44612 "EHLO mail-qv1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727162AbgARNh3 (ORCPT ); Sat, 18 Jan 2020 08:37:29 -0500 Received: by mail-qv1-f66.google.com with SMTP id n8so11983188qvg.11 for ; Sat, 18 Jan 2020 05:37:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VF7Ybre9nicDdkbJ8YLCx9ZGXACXxQfpsesRhP5xc4k=; b=EY3A6DSLTKp1/kz1PrlGIeXEHIfZ+oH6MwVnlkr7xQTR3QolUfLzcrf937teMuKRrb zujAJVMsdgkbQFnO7cdoFfEDSmlT6jfMb9+hqE49E2xj6fg4AzURPCHdn/fCXSbXhwEJ yTxjNPWuM83IaBXYefWXukRwVW8We1HyswaRf+1gQ6WUlu+ntdM8jfDaSvHUA5QTaXe9 ZSbr9yOKCstPniXl7afwYigPQOdWs3y8vaqUVQeu7emu2B+C/jljkfi9d2e9Bv/JVoBz s7xJnj4qdvZpwBrajm/Kd4AIsI8+9J48hr/ks/cqpU7LVTZ9YjpJ/sv0HCRQpfN3OnmO o3JA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VF7Ybre9nicDdkbJ8YLCx9ZGXACXxQfpsesRhP5xc4k=; b=GG/uBXneBleBQjh1wQcL6JsX3Zf12TJ96vdJxg+3LjYBUy3OYqq/FONDxXYakGpXUz Hx+421bhq3/eYgRhRXOC6QPRF9twu0+reqpia6Zwghegdup4XAnzvz8lfbmDQ1gezw/X 2YnDy1lX+dzeBHTcdYzGMUsWLyN2oiY4r4FtSSouEmYyhipg/2gwwgFVVTrJV6Blky+S MmEHNpUUJcIpp4/ag0SPe9y8MACKGP0u8DirxkfgEw4u7A7L6kL2cwIE1nsB22To1eUL CzV+/nu1UTA2NHfzLTMKomhaf6B5+S+M/g8BFQ19lxo5Q2jtsBgPCwTeh4n+igZzwTNL J/Ag== X-Gm-Message-State: APjAAAU3bV4M+4qXfDb9TBcsIk49FAs+kPza9jHdtqPRobLcCKgj2iW9 C6YcEUVPtA7BmMF/6sOgbZYsYegfoYTdH9ZyxujbFA== X-Received: by 2002:a05:6214:1103:: with SMTP id e3mr12426686qvs.159.1579354648459; Sat, 18 Jan 2020 05:37:28 -0800 (PST) MIME-Version: 1.0 References: <934E6F23-96FE-4C59-9387-9ABA2959DBBB@lca.pw> In-Reply-To: From: Dmitry Vyukov Date: Sat, 18 Jan 2020 14:37:17 +0100 Message-ID: Subject: Re: [PATCH -next] x86/efi_64: fix a user-memory-access in runtime To: Ard Biesheuvel Cc: Qian Cai , Ard Biesheuvel , Ingo Molnar , kasan-dev , linux-efi , Linux Kernel Mailing List 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 Sat, Jan 18, 2020 at 2:35 PM Ard Biesheuvel wrote: > > > On Jan 18, 2020, at 3:00 AM, Ard Biesheuvel wrote: > > > > > > Can't we just use READ_ONCE_NOCHECK() instead? > > > > My understanding is that KASAN actually want to make sure there is a no dereference of user memory because it has security implications. Does that make no sense here? > > Not really. This code runs extremely early in the boot, with a > temporary 1:1 memory mapping installed so that the EFI firmware can > transition into virtually remapped mode. > > Furthermore, the same issue exists for mixed mode, so we'll need to > fix that as well. I'll spin a patch and credit you as the reporter. If this code runs extremely early and uses even completely different mapping, it may make sense to disable KASAN instrumentation of this file in Makefile.