From: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
To: Yoann Congal <yoann.congal@smile.fr>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [scarthgap][PATCH v2 2/7] libpcap: Fix CVE-2026-31912
Date: Wed, 14 Oct 2026 10:54:09 +0200 [thread overview]
Message-ID: <db708460-55d3-4b11-aca9-5f790a57eac2@est.tech> (raw)
In-Reply-To: <DLU7MXCRDG6L.3GEYY13WESLNP@smile.fr>
On 2026-10-02 10:30, Yoann Congal wrote:
> This also drop a pcap-haiku.c hunk. Should'nt we patch pcap-haiku.cpp?
> This was before it was rewriten in C.
>
> I may have missed it for the wrynose patch but if a patch is needed, could
> you send a fix for wrynose as well?
>
> Also, please check that the backport notes are exhaustive (e.g. there is
> also a missing man patch for which a note would have been appreciated)
Hi Yoann,
I will fix and send new series and Yes, I missed about haiku.
wrynose looks correct , so no patch needed there.
Regards,
Jaipaul
next prev parent reply other threads:[~2026-10-14 8:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 19:45 [scarthgap][PATCH 0/7] libpcap: backport seven CVE fixes from 1.10.7 Jaipaul Cheernam
2026-09-15 19:45 ` [scarthgap][PATCH 1/7] libpcap: Fix CVE-2026-0799 Jaipaul Cheernam
2026-09-15 19:45 ` [scarthgap][PATCH 2/7] libpcap: Fix CVE-2026-31912 Jaipaul Cheernam
2026-09-15 19:45 ` [scarthgap][PATCH 3/7] libpcap: Fix CVE-2026-31911 Jaipaul Cheernam
2026-09-15 19:45 ` [scarthgap][PATCH 4/7] libpcap: Fix CVE-2026-6244 Jaipaul Cheernam
2026-09-15 19:45 ` [scarthgap][PATCH 5/7] libpcap: Fix CVE-2026-6554 Jaipaul Cheernam
2026-09-15 19:45 ` [scarthgap][PATCH 6/7] libpcap: Fix CVE-2026-18313 Jaipaul Cheernam
2026-09-15 19:45 ` [scarthgap][PATCH 7/7] libpcap: Fix CVE-2026-18238 Jaipaul Cheernam
2026-09-21 20:17 ` [scarthgap][PATCH v2 0/7] libpcap: backport seven CVE fixes from 1.10.7 Jaipaul Cheernam
2026-09-21 20:17 ` [scarthgap][PATCH v2 1/7] libpcap: Fix CVE-2026-0799 Jaipaul Cheernam
2026-09-21 20:17 ` [scarthgap][PATCH v2 2/7] libpcap: Fix CVE-2026-31912 Jaipaul Cheernam
2026-10-02 8:30 ` [OE-core] " Yoann Congal
2026-10-14 8:54 ` Jaipaul Cheernam [this message]
2026-09-21 20:17 ` [scarthgap][PATCH v2 3/7] libpcap: Fix CVE-2026-31911 Jaipaul Cheernam
2026-09-21 20:17 ` [scarthgap][PATCH v2 4/7] libpcap: Fix CVE-2026-6244 Jaipaul Cheernam
2026-09-21 20:17 ` [scarthgap][PATCH v2 5/7] libpcap: Fix CVE-2026-6554 Jaipaul Cheernam
2026-09-21 20:17 ` [scarthgap][PATCH v2 6/7] libpcap: Fix CVE-2026-18313 Jaipaul Cheernam
2026-09-21 20:17 ` [scarthgap][PATCH v2 7/7] libpcap: Fix CVE-2026-18238 Jaipaul Cheernam
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=db708460-55d3-4b11-aca9-5f790a57eac2@est.tech \
--to=jaipaul.cheernam@est.tech \
--cc=openembedded-core@lists.openembedded.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