From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Yoann Congal" <yoann.congal@smile.fr>, <chee.yang.lee@intel.com>,
<docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH] migration-guide: add release notes for 5.0.18
Date: Mon, 08 Jun 2026 17:28:37 +0200 [thread overview]
Message-ID: <DJ3RVZMXBB3T.129EIAP8FEH63@bootlin.com> (raw)
In-Reply-To: <DJ1G8TYU29O5.3UOXLB4S0H9RB@smile.fr>
Hi,
On Fri Jun 5, 2026 at 11:55 PM CEST, Yoann Congal wrote:
> On Fri Jun 5, 2026 at 4:18 PM CEST, Antonin Godard via lists.yoctoproject.org wrote:
>> Hi,
>>
>> How are there so many new CVE status updates for the kernel? Is it linked to a
>> recent change on Scarthgap? Could we mention it in the release notes? This seems
>> a bit out of the ordinary.
>
> I think this is linked to
> linux/generate-cve-exclusions: backport script from master branch
> https://git.openembedded.org/openembedded-core/commit/?h=scarthgap&id=66a13f93403533b95ed27eed24931aa310f8ce79
> linux-yocto/6.6: update CVE exclusions (6.6.123)
> https://git.openembedded.org/openembedded-core/commit/?h=scarthgap&id=4bdf5345c32c9e294a64d61af49ce2adabdaf1db
>
> Basically, the cve exclusion list jumped from 6.6.32 to 6.6.123 in one
> commit.
Ok, I've added this sentence at the beginning of the section:
"""
The large number of CVE updates for the ``linux-yocto`` recipe is linked to two backport
commits on :term:`OpenEmbedded-Core (OE-Core)`. See
:oecore_rev:`66a13f93403533b95ed27eed24931aa310f8ce79` and
:oecore_rev:`4bdf5345c32c9e294a64d61af49ce2adabdaf1db` for more details on these
changes.
"""
Antonin
next prev parent reply other threads:[~2026-06-08 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 10:24 [PATCH] migration-guide: add release notes for 5.0.18 chee.yang.lee
2026-06-05 14:18 ` [docs] " Antonin Godard
2026-06-05 21:55 ` Yoann Congal
2026-06-08 15:28 ` Antonin Godard [this message]
2026-06-09 7:27 ` Antonin Godard
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=DJ3RVZMXBB3T.129EIAP8FEH63@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=chee.yang.lee@intel.com \
--cc=docs@lists.yoctoproject.org \
--cc=yoann.congal@smile.fr \
/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