Created attachment 446368 [details] Simple patch to remove the message Description of problem: When an NFS volume is mounted with -onolock, any interrupted blocked locking call generates this message: kernel: do_vfs_lock: VFS is out of sync with lock manager! The message is incorrect, since the lock manager will not be used on mounts with -onolock, and is both annoying and scary on the logs. It was recently fixed upstream: http://marc.info/?t=128383914000003&r=1&w=2 Version-Release number of selected component (if applicable): kernel-2.6.18-164.2.1.el5 on the test box where it was reproduced, but pretty much any RHEL-5 kernel is affected. How reproducible: Always. Steps to Reproduce: 1. mount -onolock server:/volume /mnt 2. flock /mnt/file bash [ locks the file and spawns a new shell ] 3. flock -w 1 /mnt/file bash [ repeat ad nauseam, each gets a printk ] The "flock -w 1" is a case where it alarms out of the flock call. One can also run it without a timeout and ^C out of it, and it also gets a printk. Actual results: Incorrect message is displayed on the console and sent to the logs. Expected results: No incorrect messages.
=== In Red Hat Customer Portal Case 00320163 === --- Comment by Sammons, Eric on 9/26/2010 3:00 PM --- Customer has also expressed concerns of a possible DoS scenario here and would like to request this released as Errata.
I've incorporated this patch into my test kernels here: http://people.redhat.com/jlayton/ ...if you have a non-critical place to test them, please do so and report the results.
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-245.el5 You can download this test kernel (or newer) from http://people.redhat.com/jwilson/el5 Detailed testing feedback is always welcomed.
Reproduced in 2.6.18-244.el5 and verified in 2.6.18-245.el5.
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-2011-1065.html