From: Zdenek Kabelac <zkabelac@redhat.com>
To: chich21@mail.com
Cc: linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: Linux kernel 2.6.34.7 lvm error
Date: Mon, 04 Oct 2010 15:07:27 +0200 [thread overview]
Message-ID: <4CA9D18F.7070003@redhat.com> (raw)
In-Reply-To: <4CA99462.5050707@redhat.com>
Dne 4.10.2010 10:46, Zdenek Kabelac napsal(a):
> 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
>
So - after bisecting - it seems that commit:
39aa3cb3e8250db9188a6f1e3fb62ffa1a717678
"mm: Move vma_stack_continue into mm.h" by Stefan
had a nice 'bug-fixing' side effect which have not been mentioned in its
description - it fixes misbehaving of mlock/munlock [stack] mapping size.
So I assume this commit should be backported to stable kernels as well when
there is stack-guard patch already added.
Cc: stable@
Zdenek
next prev parent reply other threads:[~2010-10-04 13:08 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
2010-10-04 13:07 ` Zdenek Kabelac [this message]
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=4CA9D18F.7070003@redhat.com \
--to=zkabelac@redhat.com \
--cc=chich21@mail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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