<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:32:27 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-3273] mdt_mfd_open() may call mdt_handle2mfd() w/o holding med_open_lock</title>
                <link>https://jira.whamcloud.com/browse/LU-3273</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;During replay mdt_mfd_open() calls mdt_handle2mfd() with out holding the med_open_lock. This seems like an potentially unsafe walk of the med_open_head list. It later takes the lock to unlink mfd, but it does not seem to check that it has won the possible race to unlink this mfd.&lt;/p&gt;</description>
                <environment></environment>
        <key id="18708">LU-3273</key>
            <summary>mdt_mfd_open() may call mdt_handle2mfd() w/o holding med_open_lock</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</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="jhammond">John Hammond</assignee>
                                    <reporter username="jhammond">John Hammond</reporter>
                        <labels>
                            <label>mdt</label>
                            <label>patch</label>
                    </labels>
                <created>Sat, 4 May 2013 17:54:16 +0000</created>
                <updated>Thu, 19 Dec 2013 14:27:23 +0000</updated>
                            <resolved>Thu, 19 Dec 2013 14:27:23 +0000</resolved>
                                    <version>Lustre 2.4.0</version>
                                    <fixVersion>Lustre 2.5.0</fixVersion>
                    <fixVersion>Lustre 2.4.2</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                            <comments>
                            <comment id="57682" author="bzzz" created="Sat, 4 May 2013 17:56:59 +0000"  >&lt;p&gt;during replay we do not have any concurrency at the moment. literally all the replays are done within the context of special recovery thread, one by one.&lt;/p&gt;</comment>
                            <comment id="57758" author="adilger" created="Mon, 6 May 2013 19:03:06 +0000"  >&lt;p&gt;Alex, is it true that recovery is still single-threaded today?  I thought I saw issues in the past where this assumption was incorrect?  In any case, holding locks in the single-threaded case would not cause contention, and makes the code more correct for readers and for static code analysis tools.&lt;/p&gt;</comment>
                            <comment id="63870" author="spimpale" created="Thu, 8 Aug 2013 13:49:14 +0000"  >&lt;p&gt;I have submitted a patch to fix this bug here (&lt;a href=&quot;http://review.whamcloud.com/#/c/7272/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#/c/7272/&lt;/a&gt;)&lt;/p&gt;</comment>
                            <comment id="66829" author="jhammond" created="Tue, 17 Sep 2013 14:17:05 +0000"  >&lt;p&gt;Patch landed to master.&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|hzvq5j:</customfieldvalue>

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