mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Andres Freund <andres@anarazel.de>, kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: progs/test_ksyms_btf.c:37:21: error: no member named 'cpu' in 'struct rq'
Date: Fri, 4 Nov 2022 14:48:54 +0800	[thread overview]
Message-ID: <93b22dc2-76bd-f59b-aa86-836863b98b17@intel.com> (raw)
In-Reply-To: <20221029220425.p6lcwx65e4aqqkiw@awork3.anarazel.de>



On 10/30/2022 6:04 AM, Andres Freund wrote:
> Hi,
> 
> On 2022-10-27 05:02:14 +0800, kernel test robot wrote:
>> First bad commit (maybe != root cause):
>>
>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> head:   98555239e4c3aab1810d84073166eef6d54eeb3d
>> commit: 600b7b26c07a070d0153daa76b3806c1e52c9e00 tools bpftool: Fix compilation error with new binutils
>> date:   3 months ago
>> compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
>> reproduce:
>>          # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=600b7b26c07a070d0153daa76b3806c1e52c9e00
>>          git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>>          git fetch --no-tags linus master
>>          git checkout 600b7b26c07a070d0153daa76b3806c1e52c9e00
>>          make O=/tmp/kselftest headers
>>          make O=/tmp/kselftest -C tools/testing/selftests
>>
>> If you fix the issue, kindly add following tag where applicable
>> | Reported-by: kernel test robot <lkp@intel.com>
>>
>> All errors (new ones prefixed by >>):
>>
>>>> progs/test_ksyms_btf.c:37:21: error: no member named 'cpu' in 'struct rq'
>>                     out__rq_cpu = rq->cpu;
>>                                   ~~  ^
>>     progs/test_ksyms_btf.c:44:27: error: no member named 'cpu' in 'struct rq'
>>                     out__cpu_0_rq_cpu = rq->cpu;
>>                                         ~~  ^
>>     progs/test_ksyms_btf.c:48:25: error: no member named 'cpu' in 'struct rq'
>>             out__this_rq_cpu = rq->cpu;
>>                                ~~  ^
>>     3 errors generated.
>> --
>>>> progs/test_ksyms_btf_null_check.c:25:26: error: no member named 'cpu' in 'struct rq'
>>                     *(volatile int *)(&rq->cpu);
>>                                        ~~  ^
>>     1 error generated.
>> --
>>>> progs/test_ksyms_weak.c:41:29: error: no member named 'cpu' in 'struct rq'
>>                     out__existing_typed = rq->cpu;
>>                                           ~~  ^
>>     1 error generated.
> 
> I tried to reproduce this, without success. And it's not really clear to me
> how it could be related to the change either...

Hi Andres,

Sorry for the inconvenience, this error can be reproduced by `make
O=/tmp/kselftest -C tools/testing/selftests/bpf`, but it shouldn't be
related to your commit, the build of parent commit stopped in early
stage which caused the false positive.

Best Regards,
Rong Chen

> 
> Greetings,
> 
> Andres Freund
> 

      reply	other threads:[~2022-11-04  6:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26 21:02 kernel test robot
2022-10-29 22:04 ` Andres Freund
2022-11-04  6:48   ` Chen, Rong A [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=93b22dc2-76bd-f59b-aa86-836863b98b17@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=acme@redhat.com \
    --cc=andres@anarazel.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®