From: Chuck Ebbert <76306.1226@compuserve.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: "Grant Coady" <gcoady.lk@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: 2.6.17.8 - do_vfs_lock: VFS is out of sync with lock manager!
Date: Sat, 12 Aug 2006 04:58:49 -0400 [thread overview]
Message-ID: <200608120502_MC3-1-C7DD-FF7F@compuserve.com> (raw)
In-Reply-To: <9a8748490608101537y4c377fb3xcd8babbdbc29cee2@mail.gmail.com>
On Fri, 11 Aug 2006 00:37:35 +0200, Jesper Juhl wrote:
> > > >I have some webservers that have recently started reporting the
> > > >following message in their logs :
> > > >
> > > > do_vfs_lock: VFS is out of sync with lock manager!
What does this (not even compile tested) patch print?
--- 2.6.17.8-nb/fs/lockd/clntproc.c 2006-06-10 17:39:21.000000000 -0400
+++ 2.6.17.8-nb/fs/lockd/clntproc.c.new 2006-08-12 04:43:45.000000000 -0400
@@ -458,7 +458,9 @@ static void nlmclnt_locks_init_private(s
static void do_vfs_lock(struct file_lock *fl)
{
int res = 0;
- switch (fl->fl_flags & (FL_POSIX|FL_FLOCK)) {
+ unsigned char flags = fl->fl_flags & (FL_POSIX|FL_FLOCK);
+
+ switch (flags) {
case FL_POSIX:
res = posix_lock_file_wait(fl->fl_file, fl);
break;
@@ -469,8 +471,8 @@ static void do_vfs_lock(struct file_lock
BUG();
}
if (res < 0)
- printk(KERN_WARNING "%s: VFS is out of sync with lock manager!\n",
- __FUNCTION__);
+ printk(KERN_WARNING "%s: VFS is out of sync with lock manager! -- %s: %d\n",
+ __FUNCTION__, flags == FL_POSIX ? "POSIX" : "FLOCK", res);
}
/*
--
Chuck
next reply other threads:[~2006-08-12 9:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-12 8:58 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-08 14:39 2.6.17.8 - do_vfs_lock: VFS is out of sync with lock manager! Jesper Juhl
2006-08-08 14:39 ` Jesper Juhl
2006-08-09 5:53 ` Grant Coady
2006-08-09 5:53 ` Grant Coady
2006-08-09 8:07 ` Jesper Juhl
2006-08-09 8:07 ` Jesper Juhl
2006-08-10 22:37 ` Jesper Juhl
2006-08-10 22:37 ` Jesper Juhl
2006-08-11 0:30 ` Grant Coady
2006-08-11 0:30 ` Grant Coady
2006-08-13 23:08 ` Grant Coady
2006-08-13 23:08 ` Grant Coady
2006-08-17 6:49 ` Neil Brown
2006-08-17 9:58 ` Jesper Juhl
2006-08-21 3:34 ` Neil Brown
2006-08-21 19:54 ` Trond Myklebust
2006-11-21 12:43 ` Jesper Juhl
2006-11-27 9:19 ` Jesper Juhl
2007-01-29 5:08 ` Neil Brown
2007-01-29 14:16 ` [NFS] " Trond Myklebust
2007-01-30 23:42 ` Jesper Juhl
2007-02-01 22:39 ` Neil Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200608120502_MC3-1-C7DD-FF7F@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=gcoady.lk@gmail.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.