All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: chich21@mail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux kernel 2.6.34.7 lvm error
Date: Mon, 04 Oct 2010 10:46:26 +0200	[thread overview]
Message-ID: <4CA99462.5050707@redhat.com> (raw)
In-Reply-To: <8CD30F86F2A0A2B-BE8-179A8@web-mmc-m02.sysops.aol.com>

Dne 3.10.2010 11:56, chich21@mail.com napsal(a):
> With Linux kernel 2.6.34.7 from www.kernel.org the following error occurs.
> 
> Issuing this command produces error.
> 
> vgchange -ay
> 
> outputs:
> Internal error: Maps lock 14317216 < unlock 14321312
> 
> vgchange is part of lvm-tools.
> 
> This doesn't happen with kernel 2.6.34 or 2.6.34.1 from www.kernel.org.
> 
> Is there a patch for 2.6.34.x series coming for this error. As there is one
> for 2.6.35.x series.
> 
> Please CC email me related posts.


Bug is related to stack guard fix - kernel 2.6.36-rc4 has this problem fixed.
Bug is present in 2.6.36-rc3 - so something between them fixes the problem.

It looks like the [stack] mapping loses 1 page after each mlock/munlock cycle.
I'm probably going to play bisect game to find out missing fix.

https://bugzilla.redhat.com/show_bug.cgi?id=638525

Meanwhile lvm tools were also updated to read whole mapping table before
locking pages to avoid reading some mapping lines twice.

Zdenek.


  reply	other threads:[~2010-10-04  8:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-03  9:56 Linux kernel 2.6.34.7 lvm error chich21
2010-10-04  8:46 ` Zdenek Kabelac [this message]
2010-10-04 13:07   ` Zdenek Kabelac
2010-10-06 13:29     ` Stefan Bader

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=4CA99462.5050707@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=chich21@mail.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 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.