linux-kernel - Re: 2.6.13.4 - "lockd: weird return 1 for CANCEL call"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <9a8748490702210344r2f9ed9cbs892e2e5f2570d546@mail.gmail.com>
Date:	Wed, 21 Feb 2007 12:44:10 +0100
From:	"Jesper Juhl" <jesper.juhl@...il.com>
To:	"Neil Brown" <neilb@...e.de>
Cc:	nfs@...ts.sourceforge.net,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.13.4 - "lockd: weird return 1 for CANCEL call"

On 21/02/07, Neil Brown <neilb@...e.de> wrote:
> On Wednesday February 21, jesper.juhl@...il.com wrote:
> > Greetings,
> >
> > I just got a unusual message from lockd on a webserver running a
> > custom compiled 2.6.13.4 (yes it is ancient, I know).
> >
> > # uname -a
> > Linux webserv.somedomain.example 2.6.13.4 #1 SMP Wed Nov 16 10:03:05
> > CET 2005 i686 unknown
> >
> > # dmesg | tail -n 3
> > do_vfs_lock: VFS is out of sync with lock manager!
> > lockd: weird return 1 for CANCEL call
> > lockd: weird return 1 for CANCEL call
> >
> > The server seems to be running fine, so I'm not really worried, but I
> > thought maybe someone would like to know. :-)
>
> Thanks.
> Don't be worried.  They are both warning about perfectly acceptable
> (though uncommon) behaviour.  These warnings have since been removed.
>
I know the "VFS is out of sync with lock manager" warning has been
removed (I pushed quite a bit to get that done myself ;) I was just
providing context.  The one I had not seen before was the "weird
return ..." one.

> A process was interrupted while trying to get a lock, so the NFS
> client didn't know if it actually had the lock or not.
> When the process exited, the tried to cancel the lock just to be on
> the safe side and was told that it didn't own any such lock.
>
Thanks a lot for that very nice explanation.

-- 
Jesper Juhl <jesper.juhl@...il.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/