From: Romain Naour <romain.naour@gmail.com>
To: Joachim Wiberg <troglobit@gmail.com>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>,
buildroot@buildroot.org
Cc: "Jérôme Pouiller" <jezz@sysmic.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/lxc: bump to version 4.0.11
Date: Sun, 30 Jan 2022 17:36:39 +0100 [thread overview]
Message-ID: <114f25cd-b392-fbde-ce20-eef87447f1c0@gmail.com> (raw)
In-Reply-To: <87bl0t1a9o.fsf@gmail.com>
Hello Fabrice, Joachim, All,
Le 03/01/2022 à 09:41, Joachim Wiberg a écrit :
> On Sat, Jan 01, 2022 at 23:59, Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
>> The LXC 4.0 branch is supported until June 2025.
>> Only bugfixes and securitiy issues get included into the stable bugfix
>> releases, so it's always safe and recommended to keep up and run the
>> latest bugfix release.
Well it also includes new features since this version bump break lxc with all
kernel < 5.6 due to the broken fall back when the new mount API is not supported.
We have a test for lxc using a kernel 4.19 that trigger this issue [1].
See lxc.log:
(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"
[1] https://gitlab.com/buildroot.org/buildroot/-/jobs/2006798998
This issue is not yet fixed in lxc stable-4.0 branch.
Can you have a look?
Best regards,
Romain
>>
>> https://discuss.linuxcontainers.org/t/lxc-4-0-11-has-been-released/12427
>>
>> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
>
> Reviewed-by: Joachim Wiberg <troglobit@gmail.com>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-30 16:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-01 22:59 [Buildroot] [PATCH 1/1] package/lxc: bump to version 4.0.11 Fabrice Fontaine
2022-01-03 8:41 ` Joachim Wiberg
2022-01-30 16:36 ` Romain Naour [this message]
2022-02-19 9:20 ` Romain Naour
2022-02-19 15:20 ` Fabrice Fontaine
2022-02-19 16:43 ` Romain Naour
2022-02-19 17:05 ` Fabrice Fontaine
2022-01-04 17:56 ` Arnout Vandecappelle
2022-01-26 20:07 ` Peter Korsgaard
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=114f25cd-b392-fbde-ce20-eef87447f1c0@gmail.com \
--to=romain.naour@gmail.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=jezz@sysmic.org \
--cc=troglobit@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.