<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:27:08 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-2662] Build:  pthread build issue</title>
                <link>https://jira.whamcloud.com/browse/LU-2662</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;I have recreated the issue here:&lt;br/&gt;
&lt;a href=&quot;http://review.whamcloud.com/5142&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/5142&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Basically it started when strlcpy was being used in lustre/utils/liblustreapi.c. &lt;/p&gt;

&lt;p&gt;For some fun reason we get&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;...
gcc -g -Wall -fPIC -D_GNU_SOURCE -g -O2 -Werror   -o ll_dirstripe_verify ll_dirstripe_verify.o -L../../lustre/utils -llustreapi ../../libcfs/libcfs/libcfs.a 
../../libcfs/libcfs/libcfs.a(libcfs_a-user-prim.o): In function `cfs_create_thread&apos;:
/home/build/lustre-release/libcfs/libcfs/user-prim.c:241: undefined reference to `pthread_create&apos;
...
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;If you drop the small change out the system builds fine. &lt;/p&gt;</description>
                <environment>a patch pushed via git. </environment>
        <key id="17255">LU-2662</key>
            <summary>Build:  pthread build issue</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.whamcloud.com/images/icons/priorities/major.svg">Major</priority>
                        <status id="5" iconUrl="https://jira.whamcloud.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="mdiep">Minh Diep</assignee>
                                    <reporter username="keith">Keith Mannthey</reporter>
                        <labels>
                    </labels>
                <created>Mon, 21 Jan 2013 22:20:28 +0000</created>
                <updated>Tue, 15 Oct 2013 22:07:48 +0000</updated>
                            <resolved>Wed, 24 Jul 2013 22:27:08 +0000</resolved>
                                    <version>Lustre 2.4.0</version>
                                    <fixVersion>Lustre 2.4.0</fixVersion>
                    <fixVersion>Lustre 2.5.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                            <comments>
                            <comment id="51049" author="adilger" created="Wed, 23 Jan 2013 14:10:26 +0000"  >&lt;p&gt;Keith, what is the original source of this problem?  I don&apos;t see strlcpy() being used in liblustreapi.c anywhere.&lt;/p&gt;

&lt;p&gt;I can see the build failures in your patch, but we already use strlcpy() in a couple of places in the code without problems.  The compile error in &lt;a href=&quot;http://review.whamcloud.com/5142&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/5142&lt;/a&gt; is different than what is posted above:&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;Making all in mpi
../../../lustre/utils/liblustreapi.so: undefined reference to `strlcpy&apos;
collect2: ld returned 1 exit status
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;yet we do use strlcpy() successfully in cfs_get_environ() and class_set_global() for the jobid code.&lt;/p&gt;</comment>
                            <comment id="51068" author="keith" created="Wed, 23 Jan 2013 20:57:11 +0000"  >&lt;p&gt;Sorry the build test was just an example of a change Bull is wanting. I had linked to build to this LU but I didn&apos;t check to see the fails were the same.  &lt;/p&gt;

&lt;p&gt;I get the pthread issue in my local RHEL6.3 build environment without this strlcpy one.  Bull sees this same issue as well, they are the ones who found it.  Some complicated string handling code was submitted in a patch where strlcpy could have been used and it brought this issue out.&lt;/p&gt;

&lt;p&gt;The test patch is just an example of the usage Bull would like to do, it is not real code and it seems to break the build (but not on RHEL5). &lt;/p&gt;

&lt;p&gt;I wonder why my local build environment is different the the auto build server.&lt;/p&gt;</comment>
                            <comment id="51176" author="keith" created="Thu, 24 Jan 2013 22:28:56 +0000"  >&lt;p&gt;From my local build:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;cc -g -Wall -fPIC -D_GNU_SOURCE -g -O2 -Werror   -o ll_dirstripe_verify ll_dirstripe_verify.o -L../../lustre/utils -llustreapi ../../libcfs/libcfs/libcfs.a 
../../libcfs/libcfs/libcfs.a(libcfs_a-user-prim.o): In function `cfs_create_thread&apos;:
/home/build/lustre-release/libcfs/libcfs/user-prim.c:241: undefined reference to `pthread_create&apos;
collect2: ld returned 1 exit status
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;We get the error when trying to build libcfs.a &lt;/p&gt;

&lt;p&gt;The autobuild may have failed because there is no generally usable strlcpy&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;checking for strlcpy... no
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;I don&apos;t have one either but it seems the environment is different. &lt;/p&gt;

&lt;p&gt;The non-glibc version of strlcpy is in user-prim.c   I am not quite sure how RHEL5 worked without including libcfs/user_prim.h but I added it to the test build to see if the pthread will show itself in the build system.  &lt;/p&gt;

&lt;p&gt;For reference adding include libcfs/user-prim.h did not change the pthread issue on my local build.  &lt;/p&gt;

&lt;p&gt;I diffed a good build and a bad build and I really don&apos;t see anything that stands out. Same flags and same files are being used. &lt;/p&gt;

&lt;p&gt;I am going to look into this more tomorrow. &lt;/p&gt;</comment>
                            <comment id="51232" author="keith" created="Fri, 25 Jan 2013 13:35:23 +0000"  >&lt;p&gt;The real build that fails &lt;a href=&quot;http://build.whamcloud.com/job/lustre-reviews/12561/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://build.whamcloud.com/job/lustre-reviews/12561/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The adding the libcfs/user-prim.h moved along our build system&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;...
Making all in mpi
../../../lustre/utils/liblustreapi.so: undefined reference to `strlcpy&apos;
collect2: ld returned 1 exit status
make[4]: *** [cascading_rw] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.AU4Ljc (%build)
...
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
</comment>
                            <comment id="51273" author="keith" created="Fri, 25 Jan 2013 21:34:41 +0000"  >&lt;p&gt;Ok so I know a little more. &lt;/p&gt;

&lt;p&gt;The non-glibc strlxxx code resides in libcfs_a-user-prim.  It seems as are putting together liblustreapi we link in libcfs_a-user-prim.o (which requires pthread).  &lt;/p&gt;

&lt;p&gt;It seems we maybe able to add -pthread to liblustreapi in this case.  I continue to look into this. &lt;/p&gt;</comment>
                            <comment id="51274" author="keith" created="Fri, 25 Jan 2013 22:21:05 +0000"  >&lt;p&gt;It seems we need add the pthread libs to the test directory makefile for a few files.  &lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://review.whamcloud.com/5180&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/5180&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I am able to build locally with these changes. I am not sure how the build system will react. &lt;/p&gt;</comment>
                            <comment id="51275" author="keith" created="Fri, 25 Jan 2013 22:24:00 +0000"  >&lt;p&gt;I resubmitted the build test &lt;a href=&quot;http://review.whamcloud.com/5142&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/5142&lt;/a&gt; with a dependency on the makefile change.  &lt;/p&gt;</comment>
                            <comment id="51402" author="keith" created="Tue, 29 Jan 2013 12:41:39 +0000"  >&lt;p&gt;Current Status:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://review.whamcloud.com/5180&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/5180&lt;/a&gt; allows me to build local but does not allow the build system to work. &lt;/p&gt;


&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;lustre/tests/Makefile.am:1: `:=&apos;-style assignments are not portable
lustre/tests/Makefile.am:81: `:=&apos;-style assignments are not portable
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt; 

&lt;p&gt;is seen in the build system and my local setup. Investigating further.&lt;/p&gt;</comment>
                            <comment id="51429" author="keith" created="Tue, 29 Jan 2013 19:43:05 +0000"  >&lt;p&gt;I submitted another set of changes.  I converted the &apos;:=&apos; to &quot;=&quot;.  I don&apos;t get warnings on my local system with this but I am not sure it will help the build environment. &lt;/p&gt;</comment>
                            <comment id="51589" author="keith" created="Thu, 31 Jan 2013 21:42:21 +0000"  >&lt;p&gt;Well local build is till working at build system is still failing on on the unknown strlcpy. Spent some more time today looking at this and I don&apos;t quite see the next thing to try. &lt;/p&gt;</comment>
                            <comment id="51604" author="adilger" created="Fri, 1 Feb 2013 03:19:30 +0000"  >&lt;p&gt;Keith, the &quot;:=&quot; warnings are spurious.  Please start with &lt;a href=&quot;http://review.whamcloud.com/3714&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/3714&lt;/a&gt; if you want to clean that up.  That patch doesn&apos;t build for some reason, and I haven&apos;t had time to look into the details.&lt;/p&gt;

&lt;p&gt;I think the root of the problem is mostly unrelated to strlcpy() itself, but instead the &lt;tt&gt;cfs_create_thread()&lt;/tt&gt; function (also declared in user-prim.h) is the cause of the pthread dependency, which is only defined if HAVE_LIBPTHREAD is true.  This is causing the &lt;tt&gt;libcfs/libcfs/user-prim.c&lt;/tt&gt; file to reference pthread functions, but they are completely unnecessary for liblustreapi.&lt;/p&gt;

&lt;p&gt;Somehow, HAVE_LIBPTHREAD is being enabled, and by virtue of some change having added user-prim.h to get access to strlcpy() it is also dragging in the cfs_create_thread() code.  Not sure on the details, but hopefully this helps you.&lt;/p&gt;</comment>
                            <comment id="51886" author="keith" created="Wed, 6 Feb 2013 13:41:36 +0000"  >&lt;p&gt;&lt;a href=&quot;http://review.whamcloud.com/5180&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/5180&lt;/a&gt; allows me to build locally. &lt;/p&gt;

&lt;p&gt; Using in the strlxxx functions brings in the user-prim.h code that needs pthread support into liblustreapi.  I added PTHREAD_LIBS in two spots. &quot;$(LIBLUSTREAPI) $(PTHREAD_LIBS)&quot; this allows me to build locally &lt;/p&gt;

&lt;p&gt;The confusing part is the build system (&lt;a href=&quot;http://review.whamcloud.com/5142&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/5142&lt;/a&gt;) still fails with name resolution for the strlxx function.  &lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;Making all in mpi
../../../lustre/utils/liblustreapi.so: undefined reference to `strlcpy&apos;
collect2: ld returned 1 exit status
make[4]: *** [cascading_rw] Error 1
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Locally building and the build system are behaving differently.  I am a little stuck with this.  &lt;/p&gt;</comment>
                            <comment id="53095" author="keith" created="Wed, 27 Feb 2013 03:42:41 +0000"  >&lt;p&gt;I am told I need to look into &quot;lbuild&quot;. &lt;/p&gt;</comment>
                            <comment id="53753" author="keith" created="Mon, 11 Mar 2013 23:23:08 +0000"  >&lt;p&gt;Peter mentioned you were the right person to look at this. &lt;/p&gt;</comment>
                            <comment id="57408" author="keith" created="Tue, 30 Apr 2013 23:44:55 +0000"  >&lt;p&gt;Is there a outlook for this issue? &lt;/p&gt;</comment>
                            <comment id="57409" author="mdiep" created="Wed, 1 May 2013 00:00:48 +0000"  >&lt;p&gt;I don&apos;t have the bandwidth to look into this right now.&lt;/p&gt;</comment>
                            <comment id="57856" author="mdiep" created="Tue, 7 May 2013 20:28:14 +0000"  >&lt;p&gt;hmm...I built using lbuild and did not hit the failure on latest kernel. let me rebase the patch and try again&lt;/p&gt;</comment>
                            <comment id="57866" author="keith" created="Tue, 7 May 2013 21:56:16 +0000"  >&lt;p&gt;Minh can you submit a job to the build system?  That is where the issue has been seen, it was thought to be a general lbuild issue, but perhaps it is more specific to the build system. &lt;/p&gt;


&lt;p&gt;&lt;a href=&quot;http://review.whamcloud.com/4154&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/4154&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;From a month or so ago still fails to build:&lt;br/&gt;
&lt;a href=&quot;http://build.whamcloud.com/job/lustre-reviews/14514/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://build.whamcloud.com/job/lustre-reviews/14514/&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="57883" author="mdiep" created="Wed, 8 May 2013 03:53:38 +0000"  >&lt;p&gt;passed the build system: &lt;a href=&quot;http://build.whamcloud.com/job/lustre-reviews/15362/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://build.whamcloud.com/job/lustre-reviews/15362/&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="57914" author="keith" created="Wed, 8 May 2013 16:30:14 +0000"  >&lt;p&gt;Well perhaps the build system has changed enough it now works with &lt;a href=&quot;http://build.whamcloud.com/job/lustre-reviews/15362/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://build.whamcloud.com/job/lustre-reviews/15362/&lt;/a&gt; or without the patch? &lt;/p&gt;</comment>
                            <comment id="57918" author="mdiep" created="Wed, 8 May 2013 17:07:26 +0000"  >&lt;p&gt;Andreas,&lt;/p&gt;

&lt;p&gt;Should we proceed to review and land this patch &lt;a href=&quot;http://review.whamcloud.com/5180&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/5180&lt;/a&gt; ?&lt;/p&gt;</comment>
                            <comment id="57947" author="adilger" created="Wed, 8 May 2013 21:20:17 +0000"  >&lt;p&gt;If that patch isn&apos;t strictly needed to build, I would rather abandon it.  It adds pthread libraries to tools that shouldn&apos;t otherwise need them, so if the problem is gone then I&apos;m happy to abandon this patch.  It looks to me like there was some inconsistency between HAVE_LIBPTHREAD being defined in one place and not another, so it isn&apos;t surprising that some build changes cleaned it up.&lt;/p&gt;</comment>
                            <comment id="58108" author="keith" created="Fri, 10 May 2013 03:15:19 +0000"  >&lt;p&gt;I resubmitted the patch for &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-2074&quot; title=&quot;Fix &amp;#39;copy into fixed size buffer&amp;#39; errors&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-2074&quot;&gt;&lt;del&gt;LU-2074&lt;/del&gt;&lt;/a&gt; to see if the issue without the patch still occurs.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://review.whamcloud.com/4154&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/4154&lt;/a&gt; &lt;/p&gt;

</comment>
                            <comment id="58141" author="keith" created="Fri, 10 May 2013 15:17:48 +0000"  >&lt;p&gt;The build from last night failed with the issue, some sort of a fix to Master is needed. &lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;./libptlctl.a(debug.o): In function `jt_dbg_debug_kernel&apos;:
/var/lib/jenkins/workspace/lustre-reviews/arch/i686/build_type/server/distro/el6/ib_stack/inkernel/BUILD/BUILD/lustre-2.3.65/lnet/utils/debug.c:605: undefined reference to `strlcpy&apos;
../../libcfs/libcfs/libcfsutil.a(libcfsutil_a-parser.o): In function `Parser_help&apos;:
/var/lib/jenkins/workspace/lustre-reviews/arch/i686/build_type/server/distro/el6/ib_stack/inkernel/BUILD/BUILD/lustre-2.3.65/libcfs/libcfs/util/parser.c:463: undefined reference to `strlcat&apos;
collect2: ld returned 1 exit status
make[3]: *** [debugctl] Error 1
make[3]: *** Waiting for unfinished jobs....
../../libcfs/libcfs/libcfs.a(libcfs_a-user-prim.o): In function `cfs_create_thread&apos;:
/var/lib/jenkins/workspace/lustre-reviews/arch/i686/build_type/server/distro/el6/ib_stack/inkernel/BUILD/BUILD/lustre-2.3.65/libcfs/libcfs/user-prim.c:241: undefined reference to `pthread_create&apos;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

</comment>
                            <comment id="58149" author="mdiep" created="Fri, 10 May 2013 16:05:15 +0000"  >&lt;p&gt;Keith, are we working on this bug or &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-2074&quot; title=&quot;Fix &amp;#39;copy into fixed size buffer&amp;#39; errors&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-2074&quot;&gt;&lt;del&gt;LU-2074&lt;/del&gt;&lt;/a&gt;. Can we close this one and focus on the other?&lt;/p&gt;</comment>
                            <comment id="58300" author="keith" created="Mon, 13 May 2013 18:28:04 +0000"  >&lt;p&gt;This issue tracks the build issue with the Patch from 2074.  I think the context is here for dealing with the build system issue and I would rather not close this issue until the patch for &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-2074&quot; title=&quot;Fix &amp;#39;copy into fixed size buffer&amp;#39; errors&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-2074&quot;&gt;&lt;del&gt;LU-2074&lt;/del&gt;&lt;/a&gt; can build.&lt;/p&gt;</comment>
                            <comment id="59824" author="keith" created="Fri, 31 May 2013 23:04:45 +0000"  >&lt;p&gt;&lt;a href=&quot;http://review.whamcloud.com/5180&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/5180&lt;/a&gt; is needed to Build the patch for &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-2074&quot; title=&quot;Fix &amp;#39;copy into fixed size buffer&amp;#39; errors&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-2074&quot;&gt;&lt;del&gt;LU-2074&lt;/del&gt;&lt;/a&gt;. &lt;/p&gt;</comment>
                            <comment id="61530" author="keith" created="Sat, 29 Jun 2013 01:20:23 +0000"  >&lt;p&gt;Well that didn&apos;t work... &lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-2074&quot; title=&quot;Fix &amp;#39;copy into fixed size buffer&amp;#39; errors&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-2074&quot;&gt;&lt;del&gt;LU-2074&lt;/del&gt;&lt;/a&gt; was submitted right after this patch was merged but it didn&apos;t fix lbuild.  &lt;a href=&quot;http://build.whamcloud.com/job/lustre-reviews/16287/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://build.whamcloud.com/job/lustre-reviews/16287/&lt;/a&gt;&lt;/p&gt;


</comment>
                            <comment id="62938" author="mdiep" created="Wed, 24 Jul 2013 22:25:59 +0000"  >&lt;p&gt;the patch for this ticket has landed on master and a solution has been provided for &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-2074&quot; title=&quot;Fix &amp;#39;copy into fixed size buffer&amp;#39; errors&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-2074&quot;&gt;&lt;del&gt;LU-2074&lt;/del&gt;&lt;/a&gt;. This is no longe a blocker for that. closing&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                            <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzvfu7:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>6212</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10060" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Severity</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10022"><![CDATA[3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>