On Tue, Aug 15, 2006 at 02:02:50PM +0200, Jesper Juhl wrote:
> On 15/08/06, Jesper Juhl <[email protected]> wrote:
> >On 10/08/06, Jesper Juhl <[email protected]> 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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]