From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Trond Myklebust <Trond.Myklebust@netapp.com>,
Andrew Morton <akpm@osdl.org>
Subject: Re: locks_insert_block: removing duplicated lock (pid=2711 0-9223372036854775807 type=1)
Date: Tue, 15 Aug 2006 10:31:18 -0400 [thread overview]
Message-ID: <20060815143118.GC4904@fieldses.org> (raw)
In-Reply-To: <9a8748490608150502g30c2e566g7301ca5cc50778ce@mail.gmail.com>
On Tue, Aug 15, 2006 at 02:02:50PM +0200, Jesper Juhl wrote:
> On 15/08/06, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> >On 10/08/06, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> >> I've got a server running 2.6.11.11 that just reported the following in
> >dmesg :
> >>
> >> locks_insert_block: removing duplicated lock (pid=2711
> >> 0-9223372036854775807 type=1)
> >>
> >Still getting lots of these :
> >
> >Aug 15 13:53:01 server kernel: locks_insert_block: removing duplicated
> >lock (pid=3 0-9223372036854775807 type=1)
> >Aug 12 22:46:31 server kernel: locks_insert_block: removing duplicated
> >lock (pid=1036 0-9223372036854775807 type=1)
> >Aug 12 00:21:28 server kernel: locks_insert_block: removing duplicated
> >lock (pid=1020 0-9223372036854775807 type=1)
> >
> >What's the exact meaning of this?
I *think* that's harmless in that version of the code, though I'm not
sure.
Trond's made a bunch of lockd fixes since then (e.g. 09c7938c), which
probably fix it.
And that printk has been changed to a BUG(), so it better not be
triggered any more.... I certainly don't see how it could happen in the
current code.
--b.
prev parent reply other threads:[~2006-08-15 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 12:02 locks_insert_block: removing duplicated lock (pid=2711 0-9223372036854775807 type=1) Jesper Juhl
2006-08-15 11:58 ` Jesper Juhl
2006-08-15 12:02 ` Jesper Juhl
2006-08-15 14:31 ` J. Bruce Fields [this message]
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=20060815143118.GC4904@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=akpm@osdl.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox