Red Hat Bugzilla – Bug 171714
symlinks cause kernel lockup on NFS Client
Last modified: 2007-11-30 17:11:16 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7
Description of problem:
Using any kernel between 1447 and 1532 we can reliably get a machine
to lock up hard by mounting an NFS partition from another FC4 machine
and making and deleting large numbers of symlinks.
The system locks hard. NMI_WATCHDOG does not fire, ALT+SYSRQ
is locked out.
This came to light while running the attached fragment of our
product test suite.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. unpack the attached python and perl scripts
2. mount an NFS partition on the current machine
3. run looper.py from the test suite. maybe more than once.
Actual Results: Like I said, the system locks hard
Expected Results: Linux kernels should take a licking and keep on ticking
Created attachment 120369 [details]
scripts to batter an NFS mount with symlinks
Just a bit more data....
Generally both machines are 2.0+ GHz Intel P4 or P4 XEON connected by e1000 NICs
running at 1Gb. Running the same kernel.
We first spotted this on the smp kernels with both CPUs up but are also seeing
it on the smp kernels with maxcpus=1.
2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.
This is a mass-update to all currently open kernel bugs.
A new kernel update has been released (Version: 2.6.15-1.1830_FC4)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO_REPORTER state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
Closing per previous comment.