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 X-Spam-Level: X-Spam-Status: No, score=-8.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,T_DKIMWL_WL_MED,USER_IN_DEF_DKIM_WL autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CACDDC28CC0 for ; Wed, 29 May 2019 09:46:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id A163F20B7C for ; Wed, 29 May 2019 09:46:25 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="WQaepMq9" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726540AbfE2JqX (ORCPT ); Wed, 29 May 2019 05:46:23 -0400 Received: from mail-ot1-f65.google.com ([209.85.210.65]:34860 "EHLO mail-ot1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726102AbfE2JqX (ORCPT ); Wed, 29 May 2019 05:46:23 -0400 Received: by mail-ot1-f65.google.com with SMTP id n14so1399895otk.2 for ; Wed, 29 May 2019 02:46:22 -0700 (PDT) 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=GAjjxbCt4+5cgrjM01YSZfWgmJp/G0TutPxW6NVwEDU=; b=WQaepMq9EUAZlBGja8x+6V2uZFtIQk3PNlb6V0omGbOscHfRltBYF1H4Sz4MgglHTr H1HdGO5gNzCww1LCKLX4yPTpXByz8a35WWSD7LpTu2YiHF0MHykRR2b+zDM7yITrzjqm gRcrGXb7qp9VaKtASl++u8hHIu4bZa61zyGrpEYuwvmtUEOb6rFMTYBid7k+DfkGRQ/m 8+QYU3zYSg8TNsBgk67wuDSftmNvLVzhA1qRv/B113ggurbfWKEeJigFqKqSBiJXGkMk HzCxVyQYFPqPWBj01lKkBb5SH89GoRLV8PCkmiEv7qEuHSidudmbvhbk3lbyySBFo5KJ pU9w== 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=GAjjxbCt4+5cgrjM01YSZfWgmJp/G0TutPxW6NVwEDU=; b=OZnyAi4//kVVlFLLhSgStdl8NYT/yae/iCnsVhnQiqyyPU+Fs8NWj4o+wZM6BHGylX SMfvdHHg4cZh+F2w1/ois4Xqd24JGKSKmWfMlEgdjEcIW7jh5WpszuNxCfkiHbgYsXs9 egJLOGqOHeScUXsXhVeowHYk3Pz3ffNF6ygL1Ojw0oEK9n/YIrnn8buWeSQQy62K4khS wwHcGv2cx2ganChxxOVXZt0g0lc/OaIjXWgw/aEnzwL1J0rUvEFD5X7/5sAdHfVEieBi YTh48P+sYn3eP1TxSypwsC9h3hI33VweJGmMd3W+fU7wuBhUYCzVrLQGdPUcGQDv9rTS YX/g== X-Gm-Message-State: APjAAAXnqrW59Yj1wMi0YNjT00cWrxXPo5bPHA6qWlpVNp8YH1qsI5YW BkRJTIkKcTjfSDBDcjh2txs3GJq00CKaLUM8VWDemg== X-Google-Smtp-Source: APXvYqyLP4MZKeZUKtaWWXhxl83UK6QddmJ7w7xbwzhKkP69jfLbidndYG/yefEQZQ6LO2DO7d5bpShx7K/ubAx01C4= X-Received: by 2002:a9d:62cd:: with SMTP id z13mr2621053otk.251.1559123182136; Wed, 29 May 2019 02:46:22 -0700 (PDT) MIME-Version: 1.0 References: <20190528163258.260144-1-elver@google.com> <20190528163258.260144-2-elver@google.com> <20190528171942.GV2623@hirez.programming.kicks-ass.net> In-Reply-To: From: Marco Elver Date: Wed, 29 May 2019 11:46:10 +0200 Message-ID: Subject: Re: [PATCH 2/3] tools/objtool: add kasan_check_* to uaccess whitelist To: Dmitry Vyukov Cc: Peter Zijlstra , Andrey Ryabinin , Alexander Potapenko , Andrey Konovalov , Jonathan Corbet , Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , "the arch/x86 maintainers" , Arnd Bergmann , Josh Poimboeuf , "open list:DOCUMENTATION" , LKML , linux-arch , kasan-dev 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, 29 May 2019 at 10:55, Dmitry Vyukov wrote: > > On Tue, May 28, 2019 at 7:19 PM Peter Zijlstra wrote: > > > > On Tue, May 28, 2019 at 06:32:57PM +0200, Marco Elver wrote: > > > This is a pre-requisite for enabling bitops instrumentation. Some bitops > > > may safely be used with instrumentation in uaccess regions. > > > > > > For example, on x86, `test_bit` is used to test a CPU-feature in a > > > uaccess region: arch/x86/ia32/ia32_signal.c:361 > > > > That one can easily be moved out of the uaccess region. Any else? > > Marco, try to update config with "make allyesconfig" and then build > the kernel without this change. > Done. The only instance of the uaccess warning is still in arch/x86/ia32/ia32_signal.c. Change the patch to move this access instead? Let me know what you prefer. Thanks, -- Marco