On 2025-02-04T16:27:12 Takeshi Nakazato <takeshi.nakazato at nao.ac.jp> wrote: > I would like to ask about the status of LU-18071. > > https://jira.whamcloud.com/browse/LU-18071 > > I'm asking this because, as a user, I encountered a dead-lock issue when I > was working on the data analysis server based on Rocky 8, and system > administrator implied that the issue is somehow related to this ticket. > > Regarding the ticket, the patch has been provided in August last year. But > there is no update since then. Since I'm not familiar with the development > procedure of Lustre, I was wondering if you could provide an information on > how this ticket is handled after you have patch. Also, it would be really > helpful if you could give a prospect for the inclusion of the patch into > production release. > > Thank you very much for your cooperation.
The patch referenced in LU-18071 is actually a backport of a patch from LU-17871 that was landed on master. Unfortunately, the LU-18071 patch was not submitted correctly and was not updated so that it could land. I've backported a new copy as patch https://review.whamcloud.com/64219 ("LU-17871 ldlm: FLOCK ownlocks may be not set") to b2_15 that has proper attribution of the original patch. I have no estimation when it may be landed to b2_15 or included into a release tag. That said, Lustre is an open source project, and you are free to apply patches in your tree even before it is included in a "production release". This is particularly true if you are building your own packages, since you do not need to wait for a vendor to supply a new build if a patch exists. Whether a patch is in a "production release" is somewhat in the eye of the beholder - if it fixes a problem you are hitting, then it is better than not fixing the problem, regardless of whether it is in a tagged version... If you are using a vendor release on your servers, then your question is better directed to their representatives. Cheers, Andreas _______________________________________________ lustre-discuss mailing list [email protected] http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
