From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 4/4] rpm: Upgrade 4.17.1 -> 4.18rc1
Date: Sun, 18 Sep 2022 11:15:15 +0100 [thread overview]
Message-ID: <4509b1f970eb8a6561f60f752d64105a1d4d5e7e.camel@linuxfoundation.org> (raw)
In-Reply-To: <1715AA01EDB7F002.25944@lists.openembedded.org>
On Sat, 2022-09-17 at 14:49 +0100, Richard Purdie via
lists.openembedded.org wrote:
> rpm is close to release and give our release timings, update to the
> rc1 of 4.18.
>
> Includes fixes for CVE-2021-35937, CVE-2021-35938 and CVE-2021-35939
> which can't be easily backported.
>
> Refresh patches and drop the error.h patch as error() no longer used.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Looks like the changes upstream (probably related to the security fixes
) lock up during do_rootfs and do_populate_sdk in
rpmPackageFilesInstall() which calls into pseudo's openat64.
Cheers,
Richard
prev parent reply other threads:[~2022-09-18 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 13:49 [PATCH 1/4] python3-certifi: upgrade 2022.6.15 -> 2022.9.14 Richard Purdie
2022-09-17 13:49 ` [PATCH 2/4] libpng: upgrade 1.6.37 -> 1.6.38 Richard Purdie
2022-09-17 13:49 ` [PATCH 3/4] numactl: upgrade 2.0.14 -> 2.0.15 Richard Purdie
2022-09-17 13:49 ` [PATCH 4/4] rpm: Upgrade 4.17.1 -> 4.18rc1 Richard Purdie
[not found] ` <1715AA01EDB7F002.25944@lists.openembedded.org>
2022-09-18 10:15 ` Richard Purdie [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=4509b1f970eb8a6561f60f752d64105a1d4d5e7e.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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