https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-6613 Lustre <p>Though it doesn't really matter since it's just a header, the license on this file stands compared to the others (LGPLv3+ vs GPLv2/LGPLv2). Is that unintentional?</p> LU-6613

lib-dlc.h is under LGPLv3

Question/Request Minor Resolved Fixed Amir Shehata Frank Zago Mon, 18 May 2015 15:08:46 +0000 Mon, 26 Sep 2016 22:56:41 +0000 Thu, 7 Jan 2016 17:54:06 +0000 Lustre 2.8.0 0 7 <p>Yes. This is a user land header.</p> <p>Frank, thanks for pointing this out. This is indeed a mistake, and the file should be licensed under LGPL v2.1 instead of LGPL v3.0.</p> <p>Amir, can you please submit a patch to change this version in the header. It also needs a patch for 2.7.1.</p> <p>James Simmons (uja.ornl@yahoo.com) uploaded a new patch: <a href="http://review.whamcloud.com/17697" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/17697</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-6613" title="lib-dlc.h is under LGPLv3" class="issue-link" data-issue-key="LU-6613"><del>LU-6613</del></a> lnet: change lib-dlc.h to GPLv2 license<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 9cd7af01724278f5521641add2f81f9112dfd72b</p> <p>As Andreas pointed out:</p> <p>-----------------------<br/> It is fine to use the LGPL v2.1 code in a GPL v2.0-only program. LGPL v2.1 is compatible with GPL v2.0, see:<br/> <a href="http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility" class="external-link" target="_blank" rel="nofollow noopener">http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility</a><br/> <a href="http://www.gnu.org/licenses/gpl-faq.html#compat-matrix-footnote-7" class="external-link" target="_blank" rel="nofollow noopener">http://www.gnu.org/licenses/gpl-faq.html#compat-matrix-footnote-7</a></p> <p>What we can't do is change this header to be GPLv2.0 only and then use it in a non-GPL userspace program, so it needs to remain as LGPLv2.1.<br/> -----------------------</p> <p>Looking at other parts of the code we other places where GPL v2 headers are being used in LGPL code. An example is uapi_kernelcomm.h where all the HSM code is LGPL.</p> <p>The only thing that is needed here is to change from LGPLv3 to LGPLv2.1. </p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="http://review.whamcloud.com/17697/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/17697/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-6613" title="lib-dlc.h is under LGPLv3" class="issue-link" data-issue-key="LU-6613"><del>LU-6613</del></a> lnet: change lib-dlc.h to LGPLv2.1 license<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: ad77bcfd14b662ef86c71f812b11cfc203a4543f</p> <p>Landed for 2.8.0</p> Related LU-5969 Development Rank 1|hzxdjr: Rank (Obsolete) 9223372036854775807