From: Peter Korsgaard <peter@korsgaard.com>
To: Romain Naour <romain.naour@gmail.com>
Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] support/testing: test_lxc: bump kernel version to 5.15.38 for complete pidfds support
Date: Sat, 28 May 2022 13:01:06 +0200 [thread overview]
Message-ID: <87k0a5apl9.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220512204944.94312-1-romain.naour@gmail.com> (Romain Naour's message of "Thu, 12 May 2022 22:49:44 +0200")
>>>>> "Romain" == Romain Naour <romain.naour@gmail.com> writes:
> As reported by [1], the lxc test is broken since lxc >= 4.0.11.
> A patch was added to lxc 4.0.11 to use the new mount api for devpts
> setup [2] but the fall back code doesn't work when this new mount
> API is not supported. This API was added in kernel 5.6.
> (kernel 5.5)
> DEBUG conf - conf.c:lxc_setup_devpts_child:1682 - No new devpts instance will be
> mounted since no pts devices are required
> lxc-start lxc_iperf3 DEBUG conf - conf.c:lxc_setup_dev_console:1966 - Cleared
> all (0) mounts from "/dev/console"
> lxc-start lxc_iperf3 ERROR mount_utils - mount_utils.c:mount_at:661 - No such
> file or directory - Failed to mount "/proc/self/fd/44" to "/proc/self/fd/43"
> lxc-start lxc_iperf3 ERROR conf - conf.c:lxc_setup_dev_console:1988 - No such
> file or directory - Failed to mount "10(/dev/pts/0)" on "43"
> lxc-start lxc_iperf3 ERROR conf - conf.c:lxc_setup_console:2143 - No such file
> or directory - Failed to setup console
> (kernel 5.6)
> lxc-start lxc_iperf3 TRACE mount_utils - mount_utils.c:can_use_mount_api:582 -
> Kernel supports mount api
> lxc-start lxc_iperf3 TRACE mount_utils - mount_utils.c:move_detached_mount:328
> - Attach detached mount 45 to filesystem at 43
> lxc-start lxc_iperf3 TRACE conf - conf.c:lxc_setup_dev_console:1990 - Setup
> console "/dev/pts/0"
> Bump the kernel to the current LTS 5.15.38 version that fully support the
> mount API needed by lxc.
> Fixes:
> https://gitlab.com/buildroot.org/buildroot/-/jobs/2429013708
> [1] http://lists.busybox.net/pipermail/buildroot/2022-January/635251.html
> [2] https://github.com/lxc/lxc/commit/be606e16fd0fa967219d890745a425625eafe251
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed to 2022.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-05-28 11:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 20:49 [Buildroot] [PATCH] support/testing: test_lxc: bump kernel version to 5.15.38 for complete pidfds support Romain Naour
2022-05-13 19:09 ` Yann E. MORIN
2022-05-28 11:01 ` Peter Korsgaard [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=87k0a5apl9.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=romain.naour@gmail.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.