Re: [lustre-devel] Ldiskfs: kernel version triplet policy

On Nov 7, 2024, at 10:18, Else Someone <[email protected]<mailto:[email protected]>> wrote:

Hi! I've been looking into building Lustre using Nix and
[Nixpkgs](https://github.com/NixOS/nixpkgs), and I plan to upstream
Lustre support into the distribution in a foreseeable future. One of the
struggles so far has been with patch-sets for the ldiskfs module: in my
case[^1][^2] the configuration script selects the `ldiskfs-6.6-ml.series
` for the kernel version `6.6.57`, which would not apply cleanly. The
way I went about this is I reapplied the failing patches manually,
copying them into the same `patches/linux-6.6` directory, and editing
`series/ldiskfs-6.6-ml.series` in-place. The same patchset I've prepared
for `6.6.57` does not apply, for example, to `6.6.53`.


Seeing as patch series are named after major versions (minor semvers), I
wonder if the convention is to keep patches in sync with the latest
patch version in the release? If not, what is the rule? Would consider
accepting these updated patches if I were to submit them, or do you
prefer to maintain these by yourselves? Thanks!

Typically it makes sense to follow the latest upstream kernel version to
follow the point releases (assuming these are upstream kernels and
not Nix-specific kernels).

Cheers, Andreas
--
Andreas Dilger
Lustre Principal Architect
Whamcloud

_______________________________________________
lustre-devel mailing list
[email protected]
http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org