Re: Release mdadm-4.6

Xiao Ni <[email protected]>
Newsgroups gmane.linux.raid
Message-ID <CALTww291LdYTWihZ_9fJMwXVbzeTRBE-sLx5t4ORvTOOubAHNQ@mail.gmail.com>
On Mon, Mar 16, 2026 at 11:45 PM Xiao Ni <[email protected]> wrote:
>
> Hi all
>
> I'm glad to announce mdadm-4.5. It is published to both remotes

Sorry, there was a typo above. s/mdadm-4.5/mdadm-4.6/g

Regards
Xiao

> (github and kernel.org). Here are some highlights from CHANGELOG.md.
>
> # Release [mdadm-4.6](https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/log/?h=mdadm-4.6)
>
> Features:
> - Add support for new lockless bitmap from Yu Kuai
> - Add "PROBING ddf_extended" option in mdadm.conf from Martin Wilck
> - Add --detail to usage in ReadMe from Brian Matheson
>
> Fixes:
> - Fix uuid endianness mismatch issue in sysfs_rules_apply() from Abirami0904
> - Fix mdcheck: don't stop mdcheck_continue.timer from Martin Wilck
> - Deal with hot-unplugged devices in platform-intel from Jean Delvare
> - Detect corosync and libdlm via pkg-config in Makefile from Maxin John
> - Fix UEFI backward compatibility for RAID10D4 in imsm from Blazej Kucman
> - Optimize DDF header search using mmap for better performance from lilinzhe
> - Set sysfs name after assembling imsm array in incremental from Xiao Ni
> - Use creation_time for ctime in imsm container info from Xiao Ni
> - Fix sigterm variable to be volatile sig_atomic_t from Cristian Rodríguez
> - Use 64-bit off_t across both musl and glibc from Ankur Tyagi
> - Fix format overflow error in super-intel.c from Martin Wilck
> - Fix compilation errors for unused variables with GCC 16 from Martin Wilck
> - Load md_mod first to avoid module loading issues from Xiao Ni
>
> There are some important issues which led to boot failure. These issues
> have been fixed recently. It's better to make a new release. So users
> can choose a version without these problems.
> https://github.com/md-raid-utilities/mdadm/issues/249 has the details.
>
> Best Regards
> Xiao
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.