From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: lxc: fix config parsing with linux5.10
Date: Tue, 22 Dec 2020 17:27:31 +0100 [thread overview]
Message-ID: <20201222162731.pCn-XPjp78riT7ZoNxcS_jwM6KBScGRzUd7x5mHfxsg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27352@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 572 bytes --]
There's a merged pull request on the void-packages repository
lxc: fix config parsing with linux5.10
https://github.com/void-linux/void-packages/pull/27352
Description:
When upgrading to `linux5.10`, I noticed that LXC failed to parse configs, complaining about a failure in `sendfile(2)`. I was unable to start existing containers or create new ones. Upstream commit lxc/lxc@26dffd825842edf019bc17da24a6809ed51c048c already addresses this, dropping use of `sendfile` in the config parser altogether.
@CameronNemo, do you have any objections to including this patch?
prev parent reply other threads:[~2020-12-22 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 14:55 [PR PATCH] " ahesford
2020-12-22 16:23 ` CameronNemo
2020-12-22 16:27 ` ahesford [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=20201222162731.pCn-XPjp78riT7ZoNxcS_jwM6KBScGRzUd7x5mHfxsg@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).