From: Paul Barker <paul@pbarker.dev>
To: Siva Balasubramanian <sivakumar.bs@gmail.com>,
openembedded-core@lists.openembedded.org
Cc: Yoann Congal <yoann.congal@smile.fr>, Chen Qi <Qi.Chen@windriver.com>
Subject: Re: [OE-core][wrynose][PATCH] util-linux: upgrade 2.41.3 -> 2.41.5
Date: Tue, 14 Jul 2026 14:29:07 +0100 [thread overview]
Message-ID: <cca6b5d5382e36e325a075861daf8bede882bcac.camel@pbarker.dev> (raw)
In-Reply-To: <20260706115516.19878-1-sivakumar.bs@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]
On Mon, 2026-07-06 at 17:25 +0530, Siva Balasubramanian wrote:
> 2.41.4 and 2.41.5 are point releases in the same 2.41 stable series and
> contain only bug fixes and security fixes (no new features, no API/ABI
> breaks), so the upgrade complies with the stable branch policy.
>
> Among the fixes pulled in:
> - Several mount(8) TOCTOU / symlink hardening fixes (incl. CVE-2026-27456)
> - libblkid integer overflow in parse_dos_extended() and a use-after-free
> in partition probing
> - pam_lastlog2: fix libpam linking in the autotools build so
> pam_lastlog2.so links against libpam (fixes the runtime "undefined
> symbol: pam_syslog" / dlopen failure) [YOCTO #16320]
>
> Drop two backports that are now part of the release:
> - 0001-loopdev-add-LOOPDEV_FL_NOFOLLOW-to-prevent-symlink-a.patch
> (upstream f55f9906, released in 2.41.4)
> - the pam_lastlog2 libpam linking backport (upstream 5683ed6320e0,
> cherry-picked to the 2.41 stable branch as c8d0af0421f6, released in
> 2.41.5)
Hi Siva,
I just see one backport dropped in this patch. I don't see any
pam_lastlog2 backport in the current wrynose branch, is this related to
a patch that wasn't applied or something you're carrying locally?
Best regards,
--
Paul Barker
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2026-07-14 13:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 9:02 [OE-core][PATCH v1] util-linux: backport pam_lastlog2 libpam linking fix Siva Balasubramanian
2026-06-25 12:55 ` Mathieu Dubois-Briand
2026-06-25 15:06 ` Siva Kumar Balasubramanian
2026-07-06 6:30 ` [OE-core][wrynose][PATCH v2] " Siva Balasubramanian
2026-07-06 9:31 ` Yoann Congal
2026-07-06 10:56 ` Siva Kumar Balasubramanian
2026-07-06 12:16 ` Yoann Congal
2026-07-06 11:55 ` [OE-core][wrynose][PATCH] util-linux: upgrade 2.41.3 -> 2.41.5 Siva Balasubramanian
2026-07-14 13:29 ` Paul Barker [this message]
2026-07-15 11:50 ` Siva Kumar Balasubramanian
2026-07-17 13:16 ` Paul Barker
2026-07-23 6:22 ` [OE-core][wrynose][PATCH v2] " Siva Balasubramanian
2026-07-23 6:26 ` Siva Kumar Balasubramanian
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=cca6b5d5382e36e325a075861daf8bede882bcac.camel@pbarker.dev \
--to=paul@pbarker.dev \
--cc=Qi.Chen@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sivakumar.bs@gmail.com \
--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