From: "Yoann Congal" <yoann.congal@smile.fr>
To: "Ashishkumar Parmar -X (asparmar - E INFOCHIPS PRIVATE LIMITED
at Cisco)" <asparmar@cisco.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Cc: "xe-linux-external (Internal Group)" <xe-linux-external@cisco.com>
Subject: Re: [OE-core][scarthgap][PATCH 1/6] rsync: Fix CVE-2026-29518
Date: Tue, 28 Jul 2026 16:00:34 +0200 [thread overview]
Message-ID: <DKA9BTHYY16T.2Z07XWAT3C7MP@smile.fr> (raw)
In-Reply-To: <SJ0PR11MB5896A3DCBC1BB59645700280CFCB2@SJ0PR11MB5896.namprd11.prod.outlook.com>
On Tue Jul 28, 2026 at 3:50 PM CEST, Ashishkumar Parmar -X (asparmar - E INFOCHIPS PRIVATE LIMITED at Cisco) wrote:
> Hi Yoann,
>
> Thanks for reporting this.
>
> I checked the Debian 11 build failure. The Scarthgap rsync changes currently include <linux/openat2.h> and use SYS_openat2 unconditionally. The Debian 11 build headers do not define SYS_openat2, so the compilation fails.
>
> My local validation passed because the available build headers define SYS_openat2, so it did not cover this older-host case.
>
> I also checked whether upgrading to the upstream v3.2.7-sec-patches1 tag would resolve the problem. It would not: that tag has the same unconditional SYS_openat2 use and does not contain the required configure-time portability check.
>
> The current upstream v3.2.7-sec-patches branch includes the follow-up commit:
> https://github.com/RsyncProject/rsync/commit/729ec83612d43e361ada1870173b525bc0b9ebac
>
> This checks for both <linux/openat2.h> and SYS_openat2 during configure, defines HAVE_OPENAT2 only when both are available, and retains the existing fallback on older systems.
Sounds good.
>
> Once you confirm,
> I will add this follow-up to the Scarthgap series and rerun both rsync-native and rsync build validation before sending a v2.
Please also test debian11 (I used a quick container to reproduce)
Thanks!
--
Yoann Congal
Smile ECS
prev parent reply other threads:[~2026-07-28 14:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 12:13 [OE-core][scarthgap][PATCH 1/6] rsync: Fix CVE-2026-29518 Ashishkumar Parmar X (asparmar - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-06-12 12:13 ` [OE-core][scarthgap][PATCH 2/6] rsync: Fix CVE-2026-43619 Ashishkumar Parmar X (asparmar - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-06-12 12:13 ` [OE-core][scarthgap][PATCH 3/6] rsync: Fix CVE-2026-43618 Ashishkumar Parmar X (asparmar - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-06-12 12:13 ` [OE-core][scarthgap][PATCH 4/6] rsync: Fix CVE-2026-43620 Ashishkumar Parmar X (asparmar - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-06-12 12:13 ` [OE-core][scarthgap][PATCH 5/6] rsync: Fix CVE-2026-43617 Ashishkumar Parmar X (asparmar - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-06-12 12:13 ` [OE-core][scarthgap][PATCH 6/6] rsync: Fix CVE-2026-45232 Ashishkumar Parmar X (asparmar - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-06-22 11:31 ` [OE-core][scarthgap][PATCH 1/6] rsync: Fix CVE-2026-29518 Yoann Congal
2026-07-06 17:19 ` Yoann Congal
2026-07-07 9:52 ` Ashishkumar Parmar -X (asparmar - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-07-23 9:16 ` Yoann Congal
2026-07-24 4:49 ` Ashishkumar Parmar -X (asparmar - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-07-27 21:34 ` Yoann Congal
2026-07-28 13:16 ` Yoann Congal
2026-07-28 13:50 ` Ashishkumar Parmar -X (asparmar - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-07-28 14:00 ` Yoann Congal [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=DKA9BTHYY16T.2Z07XWAT3C7MP@smile.fr \
--to=yoann.congal@smile.fr \
--cc=asparmar@cisco.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=xe-linux-external@cisco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox