Bug#594756: cryptsetup: Internal error: Maps lock … < unlock …
On Sun, 2010-08-29 at 18:48 +0200, Paul Menzel wrote:
> retitle 594756 Internal error: Maps lock … < unlock …
> tag 594756 upstream patch
> quit
>
>
> [It looks like you accidentally replied to submit@bugs.debian.org too.]
>
> Am Sonntag, den 29.08.2010, 10:22 +0200 schrieb Milan Broz:
> > On 08/29/2010 08:14 AM, Paul Menzel wrote:
> > > today I noticed that after entering my password LUKS is asking for to
> > > unlock my root device, that the following message appeared. I do not
> > > know when this started.
> > >
> > > Internal error: Maps lock 13664256 < unlock 13885440
> >
> > It is not cryptsetup but lvm screaming probably.
> > Missing kernel patch from 2.6.35.3.
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d7824370e26325c881b665350ce64fb0a4fde24a
>
> Strange since Debian Sid/unstable ships 2.6.32. (It would have been
> great, if Linus had included the error message in the commit message.)
>
> Having a little bit time I found [1] searching the Web where this issue
> turned up with 2.6.34.4 and #15 suggests that this might be related to
> LVM.
>
> > Anyway, you can ignore this message for now, Debian should patch kernel.
>
> Thank you for your reply and Jonas for reassigning the report.
The reserved stack guard page was introduced in 2.6.32.19
and the above fix for it was included in 2.6.32.20.
Debian's package version 2.6.32-21 added *both* of the above so there is
no version that has the regression it fixes.
However, there is a further problem with mlock() of part of the stack,
which is fixed in 2.6.32.21 and the next Debian package version,
2.6.32-22.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
Reply to: