<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:24:38 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-2370] ldiskfs / ext4 panic with accessing to mb_groups procfs file</title>
                <link>https://jira.whamcloud.com/browse/LU-2370</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;fixed in valina kernel as&lt;br/&gt;
commit 95599968d19db175829fb580baa6b68939b320fb&lt;br/&gt;
Author: Salman Qazi &amp;lt;sqazi@google.com&amp;gt;&lt;br/&gt;
Date: Thu May 31 23:52:14 2012 -0400&lt;br/&gt;
ext4: remove mb_groups before tearing down the buddy_cache&lt;br/&gt;
We can&apos;t have references held on pages in the s_buddy_cache while we are&lt;br/&gt;
trying to truncate its pages and put the inode. All the pages must be&lt;br/&gt;
gone before we reach clear_inode. This can only be gauranteed if we&lt;br/&gt;
can prevent new users from grabbing references to s_buddy_cache&apos;s pages.&lt;br/&gt;
The original bug can be reproduced and the bug fix can be verified by:&lt;br/&gt;
while true; do mount -t ext4 /dev/ram0 /export/hda3/ram0; \&lt;br/&gt;
umount /export/hda3/ram0; done &amp;amp;&lt;br/&gt;
while true; do cat /proc/fs/ext4/ram0/mb_groups; done&lt;br/&gt;
Signed-off-by: Salman Qazi &amp;lt;sqazi@google.com&amp;gt;&lt;br/&gt;
Signed-off-by: &quot;Theodore Ts&apos;o&quot; &amp;lt;tytso@mit.edu&amp;gt;&lt;br/&gt;
Cc: stable@kernel.org&lt;/p&gt;</description>
                <environment>any ext4 based ldiskfs (may be ext3 based also)</environment>
        <key id="16740">LU-2370</key>
            <summary>ldiskfs / ext4 panic with accessing to mb_groups procfs file</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="wc-triage">WC Triage</assignee>
                                    <reporter username="shadow">Alexey Lyashkov</reporter>
                        <labels>
                            <label>patch</label>
                    </labels>
                <created>Wed, 21 Nov 2012 03:54:46 +0000</created>
                <updated>Thu, 6 Dec 2012 14:27:47 +0000</updated>
                            <resolved>Fri, 30 Nov 2012 14:14:50 +0000</resolved>
                                                    <fixVersion>Lustre 2.4.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="48167" author="shadow" created="Wed, 21 Nov 2012 03:55:50 +0000"  >&lt;p&gt;also RHEL6 (and may be other distro) have a bug with unhandled memory allocation error caused a null pointer deference.&lt;/p&gt;</comment>
                            <comment id="48490" author="keith" created="Wed, 28 Nov 2012 12:36:04 +0000"  >&lt;p&gt;Will this patch be present in RHEL7?  &lt;/p&gt;</comment>
                            <comment id="48523" author="shadow" created="Thu, 29 Nov 2012 02:28:03 +0000"  >&lt;p&gt;if you will provide a link to RHEL7 sources i may check it, i don&apos;t see that is on ftp.redhat.com. &lt;/p&gt;</comment>
                            <comment id="48603" author="pjones" created="Fri, 30 Nov 2012 14:14:50 +0000"  >&lt;p&gt;Landed for 2.4&lt;/p&gt;</comment>
                            <comment id="48741" author="keith" created="Tue, 4 Dec 2012 14:29:27 +0000"  >&lt;p&gt;I think the best checks for RHEL7 are if it is in Current Fedora.  &lt;/p&gt;

&lt;p&gt;Is there a bug open for RHEL6 and the other Distros? &lt;/p&gt;</comment>
                            <comment id="48876" author="shadow" created="Thu, 6 Dec 2012 14:27:47 +0000"  >&lt;p&gt;Keith,&lt;/p&gt;

&lt;p&gt;I have no time to check it in other distro`s, but last RHEL6.4 beta (2.6.32-343) have that bug fixed.&lt;br/&gt;
except second part of patch with error memory allocation check, that is don&apos;t fixed for now.&lt;br/&gt;
If you want - you may create a ticket in RH bugzilla.&lt;/p&gt;

&lt;p&gt;corresponded commit is one before 95599968d19db175829fb580baa6b68939b320fb in mainstream + one in past.&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|hzvcmf:</customfieldvalue>

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