Placeholder bug for the CIFS backport for 5.4. There are already some patches that have gone upstream that we'll want. My goal this time around is to keep my test kernels reasonably up to date with respect to upstream code (and with patches that I have queued for upstream).
Updating PM score.
*** Bug 239678 has been marked as a duplicate of this bug. ***
*** Bug 239685 has been marked as a duplicate of this bug. ***
*** Bug 239691 has been marked as a duplicate of this bug. ***
*** Bug 484193 has been marked as a duplicate of this bug. ***
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
in kernel-2.6.18-140.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5 Please do NOT transition this bugzilla state to VERIFIED until our QE team has sent specific instructions indicating when to do so. However feel free to provide a comment indicating that this fix has been verified.
*** Bug 462150 has been marked as a duplicate of this bug. ***
*** Bug 450015 has been marked as a duplicate of this bug. ***
*** Bug 481233 has been marked as a duplicate of this bug. ***
*** Bug 482872 has been marked as a duplicate of this bug. ***
*** Bug 486987 has been marked as a duplicate of this bug. ***
*** Bug 487362 has been marked as a duplicate of this bug. ***
*** Bug 490887 has been marked as a duplicate of this bug. ***
~~ Attention - RHEL 5.4 Beta Released! ~~ RHEL 5.4 Beta has been released! There should be a fix present in the Beta release that addresses this particular request. Please test and report back results here, at your earliest convenience. RHEL 5.4 General Availability release is just around the corner! If you encounter any issues while testing Beta, please describe the issues you have encountered and set the bug into NEED_INFO. If you encounter new issues, please clone this bug to open a new issue and request it be reviewed for inclusion in RHEL 5.4 or a later update, if it is not of urgent severity. Please do not flip the bug status to VERIFIED. Only post your verification results, and if available, update Verified field with the appropriate value. Questions can be posted to this bug or your customer or partner representative.
I didn't have time to set up any RHEL 5.4 beta system yet, but what I can say is that the kernel from [1] does not fix bz484193 (on RHEL 5.3 Server i386). [1] http://people.redhat.com/dzickus/el5/159.el5/i686/kernel-PAE-2.6.18-159.el5.i686.rpm
Ok, do you happen to have a copy of the oops message from such a crash? Could you also test the kernels on my people.redhat.com page and let me know if they fix it? http://people.redhat.com/jlayton/
Sorry, my bad - I should have been a bit more clearly. There's no oops with the above mentioned kernel (but there's a oops with the kernel on your page which I tried as well). There's just that mount error msg mount error 66 = Object is remote That's what I meant with my bugreport not being fixed - I didn't open the bug because I wanted the oops being extinguished but because I actually want to mount that share...and that's what still doesn't work.
Ok, that's expected behavior for the 5.4 kernel -- bug 484193 is specifically about an oops when mounting. Support for chasing DFS referrals at mount time is targeted for 5.5. If you see an oops with the kernels on my people.redhat.com page though, could you open a new bug for it (and post the oops message there)? If you do this, please cc me on the bug so that I can pick it up.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2009-1243.html