Received: by 10.223.164.221 with SMTP id h29csp650512wrb; Wed, 1 Nov 2017 03:13:49 -0700 (PDT) X-Google-Smtp-Source: ABhQp+RWAJ5+N/0P3A66tfdZ4OMhUvGAtYeAk/H5p+yuWvPby5LReA1PrjEBzrpCJi/z7yEx2akr X-Received: by 10.101.66.2 with SMTP id c2mr5546871pgq.403.1509531229826; Wed, 01 Nov 2017 03:13:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1509531229; cv=none; d=google.com; s=arc-20160816; b=H7APhe914NiEYozSpbt/slra8R9F76GxiBdCS1aF9IOPVHBFJUmZGa8IzEGl9geoZl 5XtHTWxXXHHdYf3aAdj4iY4TpHeIOrXJ6nUfibzmmHbhAMBKDel2S423WEOey1buSMN8 fTlwW9RykBpNVBIaCDx0/MNIp6sW8UINYfagteiiKCxzb68ZIHwskYjOdQUGTks1nen2 vn4ubvoJPuUxMtxxKUNoUtvmhOupVvtXGpdjL0I1dasyeVGUpBUcPNjbadBXN5eUlFiY w5pbAkO468rHLCECYHT3wzhZ41uXDzgRDMtvT05tZnYbIKfrlsKRXbLPEpTHPR08Z+lB sVJA== 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=0bmYVyKUCPP89rokYOjZbDJ15QommcM48/2gBnrEliE=; b=TS4EGK8miLb6O+gqmINCIs6loScALK9/5xN/02xdnqUjUha1yFKtKtwBK5cZuF5wCN d0VH6GTv394/FbjrFP6QMPf/V946TDObnlVfzsALzp+E1Ia6zaDHiM0Vsm1ua6X+/c/D eUT8h7P5gvIVK2EVS0hpeooonDawOUmMwgSqp4vRj4jflJg1XMd+8XbLyiZ/WMFRxTtH jZxRBqqog1oDnlwdinzMEbHbCpno8F+I6ZTfk5q+jKzsJeYkwhwGkQheaDWLgpB2jW5H 7poCY9be7vS2dl2V4fbEqMjq4piC1Nx+0m7UKBw4WDkGoNCJhvnAtoL18GuCfIkYOGUz Jogw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Q85Ks1zN; 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=NONE sp=NONE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s22si380988pfj.435.2017.11.01.03.13.36; Wed, 01 Nov 2017 03:13:49 -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; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Q85Ks1zN; 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=NONE sp=NONE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753688AbdKAKMQ (ORCPT + 99 others); Wed, 1 Nov 2017 06:12:16 -0400 Received: from mail-lf0-f65.google.com ([209.85.215.65]:44480 "EHLO mail-lf0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752534AbdKAKMM (ORCPT ); Wed, 1 Nov 2017 06:12:12 -0400 Received: by mail-lf0-f65.google.com with SMTP id 75so1947614lfx.1; Wed, 01 Nov 2017 03:12:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0bmYVyKUCPP89rokYOjZbDJ15QommcM48/2gBnrEliE=; b=Q85Ks1zNhdi2C1SsEMAik4W1S1P/3zYM+lZ+lyCA4wDj5zY5ml4Rl/Sk3e8ggumnn8 bqNRfoB94YT8RqMBQqSOzFvgF1DKOyw6hgTWfX1u+6oyoYPhvhWm7AI202e4pgCrgPCx RKcyHb9RxUH3s1FwLUa5KFR49t816hutlKsfSKgmUXjQJ0GbUGtivi3Nev7qNdQSbg9j xQQ/Bx8ymWHRSbXLKUvWTZ4s2mG+nhma9K0P/6NTQpDObY4cA9rXSne2kUR7h1Sjo6gh aigpsr84UONoe2UKiBTBoUMfM/GezC6VhEaQGbYajxbTtjfA58bNNyTI6BEME1rqSkwH EoIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=0bmYVyKUCPP89rokYOjZbDJ15QommcM48/2gBnrEliE=; b=CHQGUWdPrfcwH++UDteTpnn7TLgnUiekUc/OfswsalqNYjh1FHRDU/pnsSWAY8XJXL fbq18uK3JEk7QmpnOXVy6629ggB4a5IVcFl/u4/bTjvwOdIsVwXVFF0Ln4rup5UEgBMO w9CDn4krb2CVpwe3XA42+UZUkcc5oLx5eQ6pt4zyjIYKAXk9uLRpv+o3ysT0MrH5Y8Dg 0ruWEfk4lZ9QpjtLT5e2M7OJwKH9AVZ64QLnAaTy75QNrUFVrdbFfjQYOMhOAjeWapl4 YU32XprpiMev3TMGx9U9qMTc/19n1vQ/0IsAkxiM2zWCgLsmA2Rjv90oDOKBjsZqYK2N zqKA== X-Gm-Message-State: AMCzsaW5vh1QnLfeglFaOcWs/L4cqVCsxCxJYMYevpKuoxZ9ykmTWD9R hTYIL2FSlXVbEZvHMvm7+4rCc6dHSPuTQ2ZU7iN6N98r X-Received: by 10.25.92.16 with SMTP id q16mr2183697lfb.57.1509531130684; Wed, 01 Nov 2017 03:12:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.167.79 with HTTP; Wed, 1 Nov 2017 03:12:10 -0700 (PDT) In-Reply-To: <19d76d06-1aba-351c-9b7f-2c861828501c@redhat.com> References: <1508801195-5369-1-git-send-email-pintu.ping@gmail.com> <20171029142128.GB13676@yexl-desktop> <8e7d8bbb-ec51-b693-aa35-1af73c163299@redhat.com> <19d76d06-1aba-351c-9b7f-2c861828501c@redhat.com> From: Pintu Kumar Date: Wed, 1 Nov 2017 15:42:10 +0530 Message-ID: Subject: Re: [lkp-robot] [android/ion] 5fb70554d6: kernel_selftests.android.make_fail To: Laura Abbott Cc: kernel test robot , linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org, Greg Kroah-Hartman , shuah@kernel.org, dvhart@infradead.org, Bamvor Zhang Jian , Pintu Kumar , lkp@01.org 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, Nov 1, 2017 at 3:28 AM, Laura Abbott wrote: > On 10/31/2017 03:21 AM, Pintu Kumar wrote: >> On Tue, Oct 31, 2017 at 2:32 AM, Laura Abbott wrote: >>> On 10/30/2017 12:12 AM, Pintu Kumar wrote: >>>> On Sun, Oct 29, 2017 at 7:51 PM, kernel test robot >>>> wrote: >>>>> >>>>> FYI, we noticed the following commit (built with gcc-6): >>>>> >>>>> commit: 5fb70554d68e2ea032b6a28b082801d8b7b76cb8 ("android/ion: userspace test utility for ion buffer sharing") >>>>> url: https://github.com/0day-ci/linux/commits/Pintu-Agarwal/android-ion-userspace-test-utility-for-ion-buffer-sharing/20171025-022548 >>>>> >>>>> >>>>> in testcase: kernel_selftests >>>>> with following parameters: >>>>> >>>>> >>>>> test-description: The kernel contains a set of "self tests" under the tools/testing/selftests/ directory. These are intended to be small unit tests to exercise individual code paths in the kernel. >>>>> test-url: https://www.kernel.org/doc/Documentation/kselftest.txt >>>>> >>>>> >>>>> on test machine: 88 threads Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz with 64G memory >>>>> >>>>> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace): >>>>> >>>>> >>>>> >>>>> >>>>> KERNEL SELFTESTS: linux_headers_dir is /usr/src/linux-headers-x86_64-rhel-7.2-5fb70554d68e2ea032b6a28b082801d8b7b76cb8 >>>>> 2017-10-26 22:18:16 ln -sf /usr/bin/gcc-5 /usr/bin/gcc >>>>> >>>>> 2017-10-26 22:18:16 make run_tests -C android >>>>> make: Entering directory '/usr/src/linux-selftests-x86_64-rhel-7.2-5fb70554d68e2ea032b6a28b082801d8b7b76cb8/tools/testing/selftests/android' >>>>> make[1]: Entering directory '/usr/src/linux-selftests-x86_64-rhel-7.2-5fb70554d68e2ea032b6a28b082801d8b7b76cb8/tools/testing/selftests/android/ion' >>>>> gcc -I../../../../../drivers/staging/android/uapi/ -Wall -O2 -g ionapp_export.c ipcsocket.c ionutils.c -o ionapp_export >>>>> In file included from ionapp_export.c:28:0: >>>>> ionutils.h:4:17: fatal error: ion.h: No such file or directory >>>>> compilation terminated. >>>>> In file included from ionutils.c:9:0: >>>>> ionutils.h:4:17: fatal error: ion.h: No such file or directory >>>>> compilation terminated. >>>> >>>> This utility requires ion.h header file which should be included from >>>> kernel source tree: drivers/staging/android/ion/uapi/ >>>> This is already mentioned in the ion/Makefile >>>> Looks like this ion.h is not getting included inside the linux_headers_dir ? >>>> >>>> Shall I include the ion.h locally in my selftests? >>>> Or, is there a better way to include the header directly... >>>> >>>> >>> >>> >>> I can't reproduce this in any of my environments but if I had to guess, >>> it's because you have >>> >>> #include "ion.h" >>> >>> which is supposed to look in the local path. >>> >> >> I don't think this is the problem. >> It just means, first it will look into the local path, then it will >> look into the include path which is specified in the Makefile. >> And, in the Makefile I have already included the path where it exists. >> INCLUDEDIR := -I../../../../../drivers/staging/android/uapi/ >> > > Ah yeah you are right > >> I think the problem is in general, and not specific to this test. >> Because, when I manually try to install the kernel headers, I could >> not find the "ion.h" there, or none of the headers from >> drivers/staging/android/ >> # make headers_install ARCH=i386 INSTALL_HDR_PATH=../headers/ >> >> But, I can see the drivers/android/ header files. >> >> Now the question is, how to include the header files from staging >> folder to kernel headers ? >> >> As per reference from some other selftests (such as: gpio/Makefile, >> vm/Makefile, etc.), I also tried the following. >> >> ../../../../../drivers/staging/android/uapi/ion.h: >> make -C ../../../../.. headers_install >> INSTALL_HDR_PATH=$(shell pwd)/../../../../usr/ >> >> But this also does not help in installing the ion.h header file in >> kernel_header path. >> >> Any other pointers to fix this issue ? >> > > The staging uapi headers don't look to be installed with the > standard install command. This makes sense given that staging > drivers are well staging and not yet stable. > > The tools/gpio Makefile seems to do this trick to allow compilation > outside the kernel tree (it is a dependency for the gpio selftest) > > # > # We need the following to be outside of kernel tree > # > $(OUTPUT)include/linux/gpio.h: ../../include/uapi/linux/gpio.h > mkdir -p $(OUTPUT)include/linux 2>&1 || true > ln -sf $(CURDIR)/../../include/uapi/linux/gpio.h $@ > > prepare: $(OUTPUT)include/linux/gpio.h > I tried something similar, but it did not help. Or may be I could not understand how to incorporate this into my code to make it work. Basically, when I do make in gpio, it automatically does this using: make -C headers_install. But in my case, this command is not getting invoked, using the following: ../../../../../drivers/staging/android/uapi/ion.h: make -C ../../../../.. headers_install INSTALL_HDR_PATH=$(shell pwd)/../../../../usr/ https://kernelnewbies.org/KernelHeaders It says: [The correct way to address this problem is to isolate the specific interfaces that you need, e.g. a single header file that is patched in a new kernel providing the ioctl numbers for a character device used by your program. In your own program, add a copy of that source file, with a notice that it should be kept in sync with new kernel versions.] According to this, it looks like we should maintain the local copy of the header file, until it is available. I also saw a similar approach in other selftests. So, for time being shall I create a local copy of ion.h ? Thanks, Pintu > Maybe something like that needs to happen here unless Shuah has > any better ideas for headers? > > Thanks, > Laura > >> >> Thanks, >> Pintu >> >> >>> Thanks, >>> Laura > From 1582812059392151394@xxx Tue Oct 31 22:00:08 +0000 2017 X-GM-THRID: 1582662213253057274 X-Gmail-Labels: Inbox,Category Forums