<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:53:18 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-5647] Kernel update [RHEL7 3.10.0-123.8.1.el7]</title>
                <link>https://jira.whamcloud.com/browse/LU-5647</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;ul&gt;
	&lt;li&gt;An out-of-bounds memory access flaw was found in the Linux kernel&apos;s&lt;br/&gt;
system call auditing implementation. On a system with existing audit rules&lt;br/&gt;
defined, a local, unprivileged user could use this flaw to leak kernel&lt;br/&gt;
memory to user space or, potentially, crash the system. (CVE-2014-3917,&lt;br/&gt;
Moderate)&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;This update also fixes the following bugs: &lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;A bug in the mtip32xx driver could prevent the Micron P420m PCIe SSD&lt;br/&gt;
devices with unaligned I/O access from completing the submitted I/O&lt;br/&gt;
requests. This resulted in a livelock situation and rendered the Micron&lt;br/&gt;
P420m PCIe SSD devices unusable. To fix this problem, mtip32xx now checks&lt;br/&gt;
whether an I/O access is unaligned and if so, it uses the correct&lt;br/&gt;
semaphore. (BZ#1125776)&lt;/li&gt;
&lt;/ul&gt;


&lt;ul&gt;
	&lt;li&gt;A series of patches has been backported to improve the functionality of&lt;br/&gt;
a touch pad on the latest Lenovo laptops in Red Hat Enterprise Linux 7.&lt;br/&gt;
(BZ#1122559)&lt;/li&gt;
&lt;/ul&gt;


&lt;ul&gt;
	&lt;li&gt;Due to a bug in the bnx2x driver, a network adapter could be unable to&lt;br/&gt;
recover from EEH error injection. The network adapter had to be taken&lt;br/&gt;
offline and rebooted in order to function properly again. With this update,&lt;br/&gt;
the bnx2x driver has been corrected and network adapters now recover from&lt;br/&gt;
EEH errors as expected. (BZ#1107722)&lt;/li&gt;
&lt;/ul&gt;


&lt;ul&gt;
	&lt;li&gt;Previously, if an hrtimer interrupt was delayed, all future pending&lt;br/&gt;
hrtimer events that were queued on the same processor were also delayed&lt;br/&gt;
until the initial hrtimer event was handled. This could cause all hrtimer&lt;br/&gt;
processing to stop for a significant period of time. To prevent this&lt;br/&gt;
problem, the kernel has been modified to handle all expired hrtimer events&lt;br/&gt;
when handling the initially delayed hrtimer event. (BZ#1113175)&lt;/li&gt;
&lt;/ul&gt;


&lt;ul&gt;
	&lt;li&gt;A previous change to the nouveau driver introduced a bit shift error,&lt;br/&gt;
which resulted in a wrong display resolution being set with some models&lt;br/&gt;
of NVIDIA controllers. With this update, the erroneous code has been&lt;br/&gt;
corrected, and the affected NVIDIA controllers can now set the correct&lt;br/&gt;
display resolution. (BZ#1114869)&lt;/li&gt;
&lt;/ul&gt;


&lt;ul&gt;
	&lt;li&gt;Due to a NULL pointer dereference bug in the be2net driver, the system&lt;br/&gt;
could experience a kernel oops and reboot when disabling a network adapter&lt;br/&gt;
after a permanent failure. This problem has been fixed by introducing a&lt;br/&gt;
flag to keep track of the setup state. The failing adapter can now be&lt;br/&gt;
disabled successfully without a kernel crash. (BZ#1122558)&lt;/li&gt;
&lt;/ul&gt;


&lt;ul&gt;
	&lt;li&gt;Previously, the Huge Translation Lookaside Buffer (HugeTLB) allowed&lt;br/&gt;
access to huge pages access by default. However, huge pages may be&lt;br/&gt;
unsupported in some environments, such as a KVM guest on a PowerPC&lt;br/&gt;
architecture, and an attempt to access a huge page in memory would result&lt;br/&gt;
in a kernel oops. This update ensures that HugeTLB denies access to huge&lt;br/&gt;
pages if the huge pages are not supported on the system. (BZ#1122115)&lt;/li&gt;
&lt;/ul&gt;


&lt;ul&gt;
	&lt;li&gt;If an NVMe device becomes ready but fails to create I/O queues, the nvme&lt;br/&gt;
driver creates a character device handle to manage such a device.&lt;br/&gt;
Previously, a character device could be created before a device reference&lt;br/&gt;
counter was initialized, which resulted in a kernel oops. This problem has&lt;br/&gt;
been fixed by calling the relevant initialization function earlier in the&lt;br/&gt;
code. (BZ#1119720)&lt;/li&gt;
&lt;/ul&gt;


&lt;ul&gt;
	&lt;li&gt;On some firmware versions of the BladeEngine 3 (BE3) controller,&lt;br/&gt;
interrupts remain disabled after a hardware reset. This was a problem for&lt;br/&gt;
all Emulex-based network adapters using such a BE3 controller because&lt;br/&gt;
these adapters would fail to recover from an EEH error if it occurred. To&lt;br/&gt;
resolve this problem, the be2net driver has been modified to enable the&lt;br/&gt;
interrupts in the eeh_resume handler explicitly. (BZ#1121712)&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Bugs fixed (&lt;a href=&quot;https://bugzilla.redhat.com/):&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://bugzilla.redhat.com/):&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;1102571 - CVE-2014-3917 kernel: DoS with syscall auditing&lt;/p&gt;</description>
                <environment>el7&lt;br/&gt;
</environment>
        <key id="26680">LU-5647</key>
            <summary>Kernel update [RHEL7 3.10.0-123.8.1.el7]</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="bogl">Bob Glossman</assignee>
                                    <reporter username="bogl">Bob Glossman</reporter>
                        <labels>
                    </labels>
                <created>Mon, 22 Sep 2014 20:47:35 +0000</created>
                <updated>Thu, 19 Feb 2015 15:52:51 +0000</updated>
                            <resolved>Thu, 19 Feb 2015 15:52:51 +0000</resolved>
                                                    <fixVersion>Lustre 2.7.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="94662" author="agarcia" created="Mon, 22 Sep 2014 22:27:28 +0000"  >&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;4:12:20 PM&amp;#93;&lt;/span&gt; Joshua Kugler: As as result of &lt;a href=&quot;https://jira.hpdd.intel.com/browse/TEI-2392&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jira.hpdd.intel.com/browse/TEI-2392&lt;/a&gt; the new kernel will show up in our update repos as soon as it lands in the CentOS update repos.  That is why Bob didn&apos;t create a TEI ticket this time around, just the LU ticket for the Lustre team.&lt;br/&gt;
As soon as CentOS releases the update, and it hits the mirrors. Then it will be pulled in when we run our nightly repo updates.&lt;/p&gt;</comment>
                            <comment id="94730" author="bogl" created="Tue, 23 Sep 2014 16:48:32 +0000"  >&lt;p&gt;&lt;a href=&quot;http://review.whamcloud.com/12024&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/12024&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="94738" author="bogl" created="Tue, 23 Sep 2014 17:00:08 +0000"  >&lt;p&gt;kernel update landed in Centos last night so we should be good to go for building new el7 today&lt;/p&gt;</comment>
                            <comment id="107357" author="jlevi" created="Thu, 19 Feb 2015 15:52:51 +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|hzwwuv:</customfieldvalue>

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