From: Juergen Kreileder <jk@blackdown.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: lvcreate on 2.6.22.1: kernel tried to execute NX-protected page
Date: Sun, 05 Aug 2007 21:52:25 +0200 [thread overview]
Message-ID: <46B62A79.3030502@blackdown.de> (raw)
In-Reply-To: <1186343163.25667.0.camel@laptopd505.fenrus.org>
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
Arjan van de Ven wrote:
> On Sun, 2007-08-05 at 21:03 +0200, Juergen Kreileder wrote:
>> I've upgraded devmapper to 1.02.20 and lvm2 to 2.02.26. Didn't help much,
>> I just got a the same BUG again:
>>
>> kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
>> BUG: unable to handle kernel paging request at virtual address f492c1f8
>
>
> I suspect this is a module that got unloaded but still had some function
> pointer registered somewhere.....
>
> do you know if/which module that could be?
> (one trick is to compile the kernel such that you don't allow modules to
> be unloaded at all; if that makes it work it's clearly the type of bug I
> described above)
It's a static kernel, no modules. I've attached the config.
Juergen
[-- Attachment #2: config-2.6.22.1-jk1-exec-shield.gz --]
[-- Type: application/x-gzip, Size: 8526 bytes --]
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Juergen Kreileder <jk@blackdown.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, dm-devel@redhat.com
Subject: Re: lvcreate on 2.6.22.1: kernel tried to execute NX-protected page
Date: Sun, 05 Aug 2007 21:52:25 +0200 [thread overview]
Message-ID: <46B62A79.3030502@blackdown.de> (raw)
In-Reply-To: <1186343163.25667.0.camel@laptopd505.fenrus.org>
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
Arjan van de Ven wrote:
> On Sun, 2007-08-05 at 21:03 +0200, Juergen Kreileder wrote:
>> I've upgraded devmapper to 1.02.20 and lvm2 to 2.02.26. Didn't help much,
>> I just got a the same BUG again:
>>
>> kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
>> BUG: unable to handle kernel paging request at virtual address f492c1f8
>
>
> I suspect this is a module that got unloaded but still had some function
> pointer registered somewhere.....
>
> do you know if/which module that could be?
> (one trick is to compile the kernel such that you don't allow modules to
> be unloaded at all; if that makes it work it's clearly the type of bug I
> described above)
It's a static kernel, no modules. I've attached the config.
Juergen
[-- Attachment #2: config-2.6.22.1-jk1-exec-shield.gz --]
[-- Type: application/x-gzip, Size: 8526 bytes --]
next prev parent reply other threads:[~2007-08-05 19:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 19:03 lvcreate on 2.6.22.1: kernel tried to execute NX-protected page Juergen Kreileder
2007-08-05 19:46 ` Arjan van de Ven
2007-08-05 19:46 ` Arjan van de Ven
2007-08-05 19:52 ` Juergen Kreileder [this message]
2007-08-05 19:52 ` Juergen Kreileder
2007-08-16 18:45 ` SLUB problems (was Re: lvcreate on 2.6.22.1: kernel tried to execute NX-protected page) Juergen Kreileder
-- strict thread matches above, loose matches on Subject: below --
2007-08-03 19:10 lvcreate on 2.6.22.1: kernel tried to execute NX-protected page Juergen Kreileder
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=46B62A79.3030502@blackdown.de \
--to=jk@blackdown.de \
--cc=arjan@infradead.org \
--cc=dm-devel@redhat.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.