All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ihor Solodrai" <ihor.solodrai@linux.dev>
To: "Costa Shulyupin" <costa.shul@redhat.com>,
	devel@lists.centos.org, "Jerome Marchand" <jmarchan@redhat.com>
Cc: "Donald Zickus" <dzickus@redhat.com>,
	"kernel-info" <kernel-info@redhat.com>,
	bpf@vger.kernel.org, shetze@redhat.com, ngompa13@gmail.com
Subject: Re: [CentOS-devel] make dist-all-rpms fails with test_progs-no_alu32-extras Error
Date: Sat, 08 Mar 2025 20:31:08 +0000	[thread overview]
Message-ID: <3d9e83827f5aa0db2b29e0fd868eadb5f94629f0@linux.dev> (raw)
In-Reply-To: <CADDUTFzAse2p5M4iEGbVK6YVGQzfUcVYQ8qBfR-d=drQZae7-g@mail.gmail.com>

On 3/8/25 6:34 AM, Costa Shulyupin wrote:
> On Wed, 5 Mar 2025 at 00:11, Donald Zickus <dzickus@redhat.com> wrote:
>>
>> Hi,
>>
>> If anyone wants to chew on a kernel build problem on the centos mailing list.  There are multiple replies to the thread with no success.
>>
>> Cheers,
>> Don
>>
>> ---------- Forwarded message ---------
>> From: Sebastian Hetze <shetze@redhat.com>
>> Date: Sat, Mar 1, 2025 at 6:50 AM
>> Subject: [CentOS-devel] make dist-all-rpms fails with test_progs-no_alu32-extras Error
>> To: <devel@lists.centos.org>
>>
>>
>> Hi *
>>
>> I recently tried to compile a custom centos-stream-9 automotive SIG kernel and failed.
>>
>> Now I see the very same problem is present in the mainline centos-stream-9 kernel.
>>
>> When I clone the sources from https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9 on a freshly installed centos-stream-9 host, the make dist-all-rpms target fails with
>>
>> make[3]: rsync: Argument list too long
>> make[3]: *** [Makefile:768: test_progs-no_alu32-extras] Error 127
>>
>>
>> This is certainly not a problem with rsync and the ulimits are definitely sufficient to deal with this ~2000 char argument list.
>>
>> So what is going on here?
>> This rsync call appears to come from the tools/testing/selftests/bpf/Makefile.
>> The problem persists if I BUILDOPTS="-selftests" and I understand bpf to be a SKIP_TARGET by default, anyway.
>>
>>
>> Does anyone have a hint? What is missing or what am I missing?
>
> I’ve bisected the issue and identified that it was introduced by commit
> selftests/bpf: Use auto-dependencies for test objects
>
> https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/commit/a7ff7bd4cdad76f4f1c37ee7c918e201dbb7ce6e
>

Hi everyone.

I tried to reproduce the error using a centos9-stream docker image [1]
(I know it might be not exactly right), following steps from the
original thread [2].

This command:

    make -j$(nproc) DISTLOCALVERSION=_at BUILDOPTS="-selftests" dist-all-rpms

completed successfully on tag kernel-5.14.0-571.el9 [3].

Shortly after auto-dependencies change was merged, a few problems with
out-of-tree builds were discovered and fixed. The symptom was also an
rsync command failure. See relevant thread on bpf mailing list [4].

I noticed that the fixes are not merged into centos9-stream tree. I
think it's worth trying to test the build with the fixes applied [5].

It's just a guess though, as I wasn't able to reproduce the failure.

[1] https://hub.docker.com/r/dokken/centos-stream-9
[2] https://lists.centos.org/hyperkitty/list/devel@lists.centos.org/thread/N4JBZWVP2OTQXWQ52E73SBRHE6GA6XPB/
[3] https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/commit/15b5887ebd883f74aaa63ab124bc0f75770eb6b1
[4] https://lore.kernel.org/bpf/877cbfwqre.fsf@all.your.base.are.belong.to.us
[5] https://lore.kernel.org/bpf/20240916195919.1872371-1-ihor.solodrai@pm.me/

           reply	other threads:[~2025-03-08 20:31 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CADDUTFzAse2p5M4iEGbVK6YVGQzfUcVYQ8qBfR-d=drQZae7-g@mail.gmail.com>]

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=3d9e83827f5aa0db2b29e0fd868eadb5f94629f0@linux.dev \
    --to=ihor.solodrai@linux.dev \
    --cc=bpf@vger.kernel.org \
    --cc=costa.shul@redhat.com \
    --cc=devel@lists.centos.org \
    --cc=dzickus@redhat.com \
    --cc=jmarchan@redhat.com \
    --cc=kernel-info@redhat.com \
    --cc=ngompa13@gmail.com \
    --cc=shetze@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.