<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
David,</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Note to expand on this, this is not the development tree itself - the suggestion is the stable tree (2.15.8), plus a single, focused change from dev to add support for the newer kernel version. It would
<b>not</b> be advisable to run the development branch itself in production, for the reasons you give, but this is not that.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Regards,</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Patrick</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> lustre-discuss <lustre-discuss-bounces@lists.lustre.org> on behalf of Peter Jones via lustre-discuss <lustre-discuss@lists.lustre.org><br>
<b>Sent:</b> Thursday, October 8, 2026 6:39 AM<br>
<b>To:</b> David Cohen <cdavid@physics.technion.ac.il>; lustre-discuss@lists.lustre.org <lustre-discuss@lists.lustre.org><br>
<b>Subject:</b> Re: [lustre-discuss] [EXTERNAL] Re: RHEL 9.8 and 10.2 support</font>
<div> </div>
</div>
<div>
<div style="direction:ltr; font-family:Aptos,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
David</div>
<div style="direction:ltr; font-family:Aptos,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="direction:ltr; font-family:Aptos,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
I do understand your concern, but, given that the equivalent change for RHEL 9.8 client support merged to master several months ago and no changes have been made to the patch since, despite that code being run hundreds of times every day, I think that the risk
of a significant latent bug still lurking is quite slim.</div>
<div style="direction:ltr; font-family:Aptos,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="direction:ltr; font-family:Aptos,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Peter</div>
<div style="direction:ltr; font-family:Aptos,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div id="x_mail-editor-reference-message-container">
<div style="padding:3pt 0in 0in; border-width:1pt medium medium; border-style:solid none none; border-color:rgb(181,196,223) currentcolor currentcolor">
<div style="text-align:left; font-family:Aptos; font-size:12pt; color:black"><b>From:
</b>lustre-discuss <lustre-discuss-bounces@lists.lustre.org> on behalf of David Cohen via lustre-discuss <lustre-discuss@lists.lustre.org><br>
<b>Date: </b>Thursday, October 8, 2026 at 1:21\u202fAM<br>
<b>To: </b>lustre-discuss@lists.lustre.org <lustre-discuss@lists.lustre.org><br>
<b>Subject: </b>Re: [lustre-discuss] [EXTERNAL] Re: RHEL 9.8 and 10.2 support<br>
<br>
</div>
</div>
<div id="x_mail-editor-reference-message-body">
<div class="x_ms-outlook-mobile-reference-message x_skipProofing" style="direction:ltr">
</div>
<div class="x_ms-outlook-mobile-reference-message x_skipProofing" style="direction:ltr">
I'm quite hesitant to put into production clients compiled from the development tree.</div>
<div class="x_ms-outlook-mobile-reference-message x_skipProofing" style="direction:ltr">
Aren't they still in development and not officially released because they are not yet ready, with potentially a major bug lurking behind the corner.</div>
<div class="x_ms-outlook-mobile-reference-message x_skipProofing" style="direction:ltr">
That being said, I might need to gamble and use those RPMs compiled from the 2.15 and 2.18 trees for el9.8 and el10.2, as this is holding back new installations and upgrades for way too many months now.</div>
<div class="x_ms-outlook-mobile-reference-message x_skipProofing" style="direction:ltr">
<br>
</div>
<div class="x_ms-outlook-mobile-reference-message x_skipProofing" style="direction:ltr">
How do other cluster managers deal with the risk?</div>
<div class="x_ms-outlook-mobile-reference-message x_skipProofing" style="direction:ltr">
Do you run outdated and vulnerable kernels or development Lustre clients?</div>
<div class="x_ms-outlook-mobile-reference-message x_skipProofing" style="direction:ltr">
<br>
</div>
<div class="x_ms-outlook-mobile-reference-message x_skipProofing" style="direction:ltr">
<br>
</div>
<div class="x_ms-outlook-mobile-reference-message x_skipProofing" style="direction:ltr">
<br>
</div>
<div class="x_ms-outlook-mobile-reference-message x_skipProofing" style="direction:ltr">
<br>
</div>
<div class="x_gmail_attr" style="direction:ltr">On Fri, Sep 18, 2026 at 10:39\u202fPM Kaizaad Bilimorya via lustre-discuss <<a href="mailto:lustre-discuss@lists.lustre.org" data-outlook-id="4e2dc314-0104-420f-89d4-007013666906">lustre-discuss@lists.lustre.org</a>>
wrote:</div>
<blockquote style="margin:0px 0px 0px 0.8ex; padding-left:1ex; border-left:1px solid rgb(204,204,204)">
<div class="x_gmail_quote" style="direction:ltr">Hello Fokke,</div>
<div class="x_gmail_quote" style="direction:ltr">Thank you for doing this, it was very helpful. I'll just add our build notes here too in case someone else finds them useful:</div>
<div class="x_gmail_quote" style="direction:ltr"><br>
</div>
<div class="x_gmail_quote" style="direction:ltr"><span style="font-family:monospace"><b>* AlmaLinux release 9.8, Kernel
</b></span><b>5.14.0-687.44.1.el9_8.x86_64</b><span style="font-family:monospace"><br>
git clone git://<a href="http://git.whamcloud.com/fs/lustre-release.git" target="_blank" data-outlook-id="d2eeb869-0ef1-4534-95e6-0be4ed787d79">git.whamcloud.com/fs/lustre-release.git</a> lustre-client<br>
cd lustre-client/<br>
git checkout tags/2.15.8<br>
<b>- Fix for "/linux-time.h:238:9: error: implicit declaration of function 'from_timer'; did you mean 'mod_timer'? [-Werror=implicit-function-declaration]" issue where the from_timer() macro was renamed in recent Linux kernel versions<br>
</b>git pull <a href="https://review.whamcloud.com/fs/lustre-release" target="_blank" data-outlook-id="a66b873d-076e-4c7a-abad-5cbc10ef913d">
https://review.whamcloud.com/fs/lustre-release</a> refs/changes/97/65797/7<br>
sh autogen.sh<br>
./configure --disable-iokit --disable-gss --disable-gss-keyring --disable-server --disable-tests --enable-client<br>
make rpms</span></div>
<div class="x_gmail_quote" style="direction:ltr"><br>
</div>
<div class="x_gmail_quote" style="direction:ltr">Thanks</div>
<div class="x_gmail_quote" style="direction:ltr">Kaizaad</div>
<div class="x_gmail_quote" style="direction:ltr; font-family:arial,sans-serif">--</div>
<div class="x_gmail_signature" style="direction:ltr"><span style="font-family:arial,sans-serif; color:rgb(34,34,34)">Kaizaad Bilimorya<br>
Systems Administrator - SHARCNET | </span><span style="font-family:arial,sans-serif; color:rgb(17,85,204)"><a href="http://www.sharcnet.ca/" target="_blank" data-outlook-id="0e60cdae-85f1-4610-9e1e-2dac383778d2" style="color:rgb(17,85,204)">http://www.sharcnet.ca</a></span><br>
<span style="font-family:arial,sans-serif; color:rgb(0,0,0)">Digital Research Alliance of Canada |
</span><span style="color:rgb(17,85,204)"><a href="https://www.alliancecan.ca/" target="_blank" data-outlook-id="fdb5032d-4592-4c5c-ba03-3e8ff1fdbb3e" style="color:rgb(17,85,204)">https://www.alliancecan.ca</a></span></div>
<div class="x_gmail_quote" style="direction:ltr"><br>
</div>
<div class="x_gmail_quote" style="direction:ltr"><br>
</div>
<div class="x_gmail_attr" style="direction:ltr">On Mon, Jun 29, 2026 at 7:41\u202fAM Fokke Dijkstra via lustre-discuss <<a href="mailto:lustre-discuss@lists.lustre.org" target="_blank" data-outlook-id="bdc6bf74-f235-49dd-853d-a1bfd212ab75">lustre-discuss@lists.lustre.org</a>>
wrote:</div>
<blockquote style="margin:0px 0px 0px 0.8ex; padding-left:1ex; border-left:1px solid rgb(204,204,204)">
<div class="x_gmail_quote" style="direction:ltr">I managed to create a patched version of the lustre-client-dkms 2.15.8 rpm, which fixes the issue that the kernel modules cannot be compiled on our Alma Linux 9.8 client nodes.<br>
Since thousands of users can login on or submit jobs to these clients we absolutely need to be able to quickly fix privilege escalation exploits on these nodes.<br>
<br>
Here is a summary of the way I was able to rebuild the lustre-client-dkms rpm:<br>
<br>
The patches for the new kernels can be found via: <a href="https://jira.whamcloud.com/browse/LU-20071" target="_blank" data-outlook-id="dbbdd422-ad6c-450b-a58e-2da4871d49f0">
https://jira.whamcloud.com/browse/LU-20071</a><br>
where LU-20071 is the label for the new Red Hat 9.8 release. I assume that a similar procedure can be followed in the future for Red Hat 9.9 and its derivatives.<br>
Note that in our case we wanted to fix the LTS release 2.15.8. So look for the branch b2_15 on the LU-20071 page. This specific patch can be found at:<br>
<a href="https://review.whamcloud.com/c/fs/lustre-release/+/65797" target="_blank" data-outlook-id="35e56393-c7c9-40fb-86ab-ac1f674b64aa">https://review.whamcloud.com/c/fs/lustre-release/+/65797</a><br>
Figuring this out took some time, as I did not know the structure of the build system, and I first tried to use the patch for the latest release, which would not apply.<br>
<br>
After this I used the following procedure to build an updated lustre-client-dkms rpm:<br>
<br>
1. Download the Lustre source rpm from <a href="https://downloads.whamcloud.com/public/lustre/latest-release/el9.7/client/SRPMS/lustre-client-dkms-2.15.8-1.el9.src.rpm" target="_blank" data-outlook-id="6fc83ac2-b084-4813-8cc4-fa25100676e5">
https://downloads.whamcloud.com/public/lustre/latest-release/el9.7/client/SRPMS/lustre-client-dkms-2.15.8-1.el9.src.rpm</a><br>
2. Install the rpm using:<br>
rpm -i lustre-client-dkms-2.15.8-1.el9.src.rpm<br>
3. Go the the ~/rpmbuild/SOURCES directory and unpack the source file<br>
tar xzf lustre-2.15.8.tar.gz<br>
4. Download the patch from <a href="https://review.whamcloud.com/c/fs/lustre-release/+/65797" target="_blank" data-outlook-id="554cc0b3-60ab-4309-8a92-50175d2ba6c8">
https://review.whamcloud.com/c/fs/lustre-release/+/65797</a>, which can be downloaded using the "DOWNLOAD" link. I selected c131e65.diff.zip<br>
5. Unzip the patch into c131e65.diff<br>
6. Apply the patch using something like:<br>
cd lustre-2.15.8<br>
patch -p1 < ../c131e65.diff<br>
cd ..<br>
7. Create an updated source tar file:<br>
tar czf lustre-2.15.8.tar.gz lustre-2.15.8<br>
8. Fix the hardcoded buildid in the spec file, by changing it from 1 to 2, so the line reads:<br>
%define buildid 2<br>
9. Build the rpm (client without zfs, but with ldiskfs for our use case):<br>
rpmbuild -ba rpmbuild/SPECS/lustre-dkms.spec --without servers --without zfs --with ldiskfs<br>
<br>
This results in rpmbuild/RPMS/noarch/lustre-client-dkms-2.15.8-2.el9.noarch.rpm<br>
<br>
Installing this rpm, together with lustre-client-2.15.8-1.el9.x86_64.rpm resulted in a working client on Alma Linux 9.8. I've tested some nodes using the IOR benchmark.<br>
<br>
I hope these instructions are helpful to others. Please let me know if you have suggestions to improve the procedure.</div>
<div class="x_gmail_quote" style="direction:ltr"><br>
</div>
<div class="x_gmail_quote" style="direction:ltr">Kind regards,</div>
<div class="x_gmail_quote" style="direction:ltr"><br>
</div>
<div class="x_gmail_quote" style="direction:ltr">Fokke Dijkstra</div>
<div class="x_gmail_quote" style="direction:ltr"><br>
</div>
<div class="x_gmail_attr" style="direction:ltr">Op di 9 jun 2026 om 19:07 schreef Mohr, Rick <<a href="mailto:mohrrf@ornl.gov" target="_blank" data-outlook-id="6da0758f-b559-4158-9dfb-6384e75f8b29">mohrrf@ornl.gov</a>>:</div>
<blockquote style="margin:0px 0px 0px 0.8ex; padding-left:1ex; border-left:1px solid rgb(204,204,204)">
<div class="x_gmail_quote">Looking through my scripts, the configure command was run with the following options (with paths to dirs substituted for variables) after the patch had been applied to the source code:<br>
<br>
configure --with-linux=$KERN_DIR --with-linux-obj=$KERN_OBJ_DIR --with-o2ib=$OFED_DIR --disable-gss --disable-gss-keyring --disable-server --disable-tests --disable-iokit --with-mds-max-threads=8192 --enable-mpitests=yes<br>
<br>
Then I just ran "make rpms" to create the packages. Everything was pretty straightforward, although not all the options I used would necessarily be needed at another site.<br>
<br>
--Rick<br>
<br>
<br>
\ufeffOn 6/4/26, 12:35 PM, "Mohr, Rick" <<a href="mailto:mohrrf@ornl.gov" target="_blank" data-outlook-id="c0d43632-2805-4442-ad02-17a766f3f56a">mohrrf@ornl.gov</a> <mailto:<a href="mailto:mohrrf@ornl.gov" target="_blank" data-outlook-id="ce852a3d-29fc-4a71-9cf4-77409979414b">mohrrf@ornl.gov</a>>>
wrote:<br>
<br>
<br>
Well, I actually built the client using a wrapper script that James Simmons wrote to manage git checkouts, patch application, etc. so the steps were hidden by that process. I'll see if I can dig out the underlying commands and post them here.<br>
<br>
<br>
--Rick<br>
<br>
<br>
<br>
<br>
</div>
</blockquote>
<div class="x_gmail_quote" style="direction:ltr"><br>
</div>
<div class="x_gmail_quote" style="direction:ltr"><br>
</div>
<div class="x_gmail_quote">--</div>
<div class="x_gmail_signature" style="direction:ltr">Fokke Dijkstra <a href="mailto:f.dijkstra@rug.nl" target="_blank" data-outlook-id="b657ade6-0b7a-44fc-8814-47e3698ff61e">
<f.dijkstra@rug.nl></a><br>
Team High Performance Computing</div>
<div class="x_gmail_signature" style="direction:ltr">Center for Information Technology, University of Groningen<br>
Postbus 11044, 9700 CA Groningen, The Netherlands<br>
<br>
</div>
<div class="x_gmail_quote">_______________________________________________<br>
lustre-discuss mailing list<br>
<a href="mailto:lustre-discuss@lists.lustre.org" target="_blank" data-outlook-id="8994f81a-6965-45bb-ad50-df5743bc85de">lustre-discuss@lists.lustre.org</a><br>
<a href="http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org" target="_blank" rel="noreferrer" data-outlook-id="db53402d-7e79-435d-895a-503eacc57976">http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org</a></div>
</blockquote>
<div class="x_gmail_quote">--<br>
lustre-discuss mailing list<br>
<a href="mailto:lustre-discuss@lists.lustre.org" target="_blank" data-outlook-id="0635bcc6-975d-4b0b-97b3-51170b8037d9">lustre-discuss@lists.lustre.org</a><br>
<a href="http://lists.lustre.org/mailman/listinfo/lustre-discuss_lists.lustre.org" target="_blank" rel="noreferrer" data-outlook-id="ac56a2e9-7c2c-406a-8636-55f1150ac768">http://lists.lustre.org/mailman/listinfo/lustre-discuss_lists.lustre.org</a></div>
</blockquote>
</div>
</div>
</div>
</body>
</html>