<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:22:19 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-2095] Trival fix for lustre/utils/wiretest.c</title>
                <link>https://jira.whamcloud.com/browse/LU-2095</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Trivial fix for lustre/utils/wiretest.c&lt;/p&gt;
</description>
                <environment></environment>
        <key id="16261">LU-2095</key>
            <summary>Trival fix for lustre/utils/wiretest.c</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="5" iconUrl="https://jira.whamcloud.com/images/icons/priorities/trivial.svg">Trivial</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="6">Not a Bug</resolution>
                                        <assignee username="keith">Keith Mannthey</assignee>
                                    <reporter username="keith">Keith Mannthey</reporter>
                        <labels>
                    </labels>
                <created>Fri, 5 Oct 2012 13:20:24 +0000</created>
                <updated>Mon, 8 Oct 2012 12:59:50 +0000</updated>
                            <resolved>Mon, 8 Oct 2012 12:59:50 +0000</resolved>
                                    <version>Lustre 2.4.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                            <comments>
                            <comment id="46090" author="adilger" created="Sat, 6 Oct 2012 15:31:59 +0000"  >&lt;p&gt;Sorry, but coming here from the patch to find out the reason behind the patch, I don&apos;t find anything of use.  Even if the change &lt;em&gt;were&lt;/em&gt; trivial (which in this case it is not, and would have potentially been a serious problem in the network protocol) the patch and bug deserve a clear explanation of what is being fixed, and why it is trivial.&lt;/p&gt;

&lt;p&gt;I &lt;em&gt;think&lt;/em&gt; that you might have missed the extra zero at the end of the OBD_CONNECT_LIGHTWEIGHT definition (0x1000000000000ULL), and thought it conflicted with OBD_CONNECT_GRANT_PARAM, which is 0x100000000000ULL?  Having that kind of explanation in the bug and/or the commit comment would make your reasoning clear. &lt;/p&gt;</comment>
                            <comment id="46183" author="keith" created="Mon, 8 Oct 2012 12:59:36 +0000"  >&lt;p&gt;Sorry this got on your radar, I will take more care in the future. I was reviewing another patch in this same code area and noticed that the params had skipped order yet were still in the same logical block and that logic was being extended. A little while later I had seen that this also appeared in another wiretest.c and was going to abandon the change to take a bit better look at the situation.  I see that it would have caused quite a problem. &lt;/p&gt;

&lt;p&gt;It was per-mature for me to submit a patch and I knew it not too long after pushing it via git. I should have invested a bit more time to carefully review the situation before the initial submission. &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|hzv57r:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>4378</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>