Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp4221774yba; Tue, 9 Apr 2019 13:56:39 -0700 (PDT) X-Google-Smtp-Source: APXvYqypeLw6y8o9Q3a0OE0q5+ofqzbAbTyCvj2ariMqKrT5Jt3tF6GAFMd0zUSU9U5rERp2WzhP X-Received: by 2002:aa7:943b:: with SMTP id y27mr15317576pfo.59.1554843399192; Tue, 09 Apr 2019 13:56:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554843399; cv=none; d=google.com; s=arc-20160816; b=i/k7ISSTePjvFpF3BEB1sdJoWkFmjcuGfdn8E/JC99cuwaMpar9YGrUk+1hdkGe4Tx Lx2n4yXwOIkyWlo0b0W/bQtTfeE4qDx4xc2tUqPK5coX02c7vxnnkIUemIukaV7iBXLd S2yRRUsBSbXpDqyALGrxM6AogqRtSGR/cyByMxL14rfC3AfsV56yah3lIWveQnNmuieJ 2K9TYLBDXYrGOVyIUX0ZqhMvqtBj1gtWdMNDvFj+HaWd8sWzJZlQ7NDpiWH1Uw1SY5J1 v+qum60jt2k1hNRtkMYelobpphjP5ZJYh4kOj4dELwzfW/bcShyImhIruPCFmaJz0OtO +P+A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id; bh=6xw5MhBdzd6LqPXyDcYeGxSqRgZdNWj37BsHLGjFQ5Y=; b=p9ztoEGKJ7zVwOGDnnor/KoNMBDqhUUuw/5DB1hA32p0eRexdCxi8XKKCJ5sHVF2XC anZwJ1H5UZd7OqGuM2YKRNsiRUF0APDmpNdEbpItYxji2NPSlpZsRNaN1fwxneFx/rrM Dt8dfH+/HGiNjhozcBJ/K6UazY+73ho1fSeKotDG3hfW/7PjzR8g1MSmFZbtQkmyhzU6 zgx5gBy9aDqjYY3TxaL4F/cCtCr2JbaNcfLQHwL6sUNugav6CfUtT3p7L6kltDKtjGri vnq6D1T2pINUrKz0TvifAkYJSKUh1F8bYQKv1A77Vbe4qlg3+u2N+kCXQtjtmqDm6LGt PRCg== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=tiscali.nl Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h70si13655587pge.520.2019.04.09.13.56.23; Tue, 09 Apr 2019 13:56:39 -0700 (PDT) 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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=tiscali.nl Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726748AbfDIUyz (ORCPT + 99 others); Tue, 9 Apr 2019 16:54:55 -0400 Received: from lb2-smtp-cloud9.xs4all.net ([194.109.24.26]:58298 "EHLO lb2-smtp-cloud9.xs4all.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726479AbfDIUyy (ORCPT ); Tue, 9 Apr 2019 16:54:54 -0400 Received: from xps13 ([83.160.161.190]) by smtp-cloud9.xs4all.net with ESMTPSA id DxlZhRJXuiLOmDxlch53S7; Tue, 09 Apr 2019 22:54:52 +0200 Message-ID: <023f28b1990577648c33281e1f4588d0abc8aa69.camel@tiscali.nl> Subject: Re: CONFIG_* symbols in UAPI headers? From: Paul Bolle To: Christoph Hellwig , Jie Zhang Cc: Mike Frysinger , David Howells , Arnd Bergmann , linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org Date: Tue, 09 Apr 2019 22:54:49 +0200 In-Reply-To: <10ca99831556bed2849e16caa5a4810628dc320c.camel@tiscali.nl> References: <20190408124640.GA607@lst.de> <10ca99831556bed2849e16caa5a4810628dc320c.camel@tiscali.nl> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 (3.28.5-3.fc28) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfAfFDH/8l/gdX5Z/nU3yD7Q9gZAmeeCNsjPAX+xaubSqHFnEx7wdLCdrmFUf6RAfLRlLGqpDuiBgLI+ce56lETx4JzdhZXliWy+Cvryp+M3HT6rQwOP/ 5GkeDK0ibh7xbTIfewzMhoSxd17G4G84kTd1im5rYilsSS7WM7aOrSs9ppiv++K6QFxVLudhaTlomskflGP391ya6xDIUSaTolsvyI8FyWzkRoZmm0kNNHYi TM4WkOLnMI59vzQGXyNyedqmbUPMTxu3G7JmsmNDPaBDucfrFpOEqW/TC7BB01/5y6HghRj3OLe3D2yRK297JMwPsdfSTuY9ECGQmPvf9z0= Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Paul Bolle schreef op di 09-04-2019 om 21:11 [+0200]: > Does it still apply? It does, cleanly. Output is (for v5.1-rc4): ./usr/include/asm-generic/fcntl.h:119: leaks CONFIG_64BIT to userspace where it is not valid ./usr/include/asm-generic/mman-common.h:22: leaks CONFIG_MMAP_ALLOW_UNINITIALIZED to userspace where it is not valid ./usr/include/linux/elfcore.h:62: leaks CONFIG_BINFMT_ELF_FDPIC to userspace where it is not valid ./usr/include/linux/flat.h:17: leaks CONFIG_BINFMT_SHARED_FLAT to userspace where it is not valid ./usr/include/linux/atmdev.h:104: leaks CONFIG_COMPAT to userspace where it is not valid ./usr/include/linux/pktcdvd.h:37: leaks CONFIG_CDROM_PKTCDVD_WCACHE to userspace where it is not valid ./usr/include/linux/raw.h:17: leaks CONFIG_MAX_RAW_DEVS to userspace where it is not valid ./usr/include/linux/hw_breakpoint.h:27: leaks CONFIG_HAVE_MIXED_BREAKPOINTS_REGS to userspace where it is not valid ./usr/include/linux/eventpoll.h:82: leaks CONFIG_PM_SLEEP to userspace where it is not valid ./usr/include/asm/auxvec.h:14: leaks CONFIG_IA32_EMULATION to userspace where it is not valid ./usr/include/asm/mman.h:7: leaks CONFIG_X86_INTEL_MEMORY_PROTECTION_KEYS to userspace where it is not valid Which suggests it might be doable to silence these warnings. Paul Bolle