From: Mikael Berthe <bmikael@lists.lilotux.net>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Kernel crash (2.4.27 + DeviceMapper + grsecurity)
Date: Wed, 25 Aug 2004 23:05:27 +0200 [thread overview]
Message-ID: <20040825210527.GK21691@lilotux.net> (raw)
Hi,
I am wondering if some people are running a 2.4.27 kernel with both
device-mapper and grsecurity.
I've been using these patches with the 2.4.25 and 2.4.26 kernel without
trouble.
Since I have upgraded to 2.4.27, I have experienced two system crashes.
I have no oops, but using a serial cable and Magic sys keys, I can see
that these two crashes happened at 06:25 during logs rotation:
savelog S 00000000 3948 18480 24071 22315 (NOTLB)
mv R current 8 22315 18480 (NOTLB)
Each time the last process is "mv" (stuck in a system call).
The EIP seems to show that the system is stuck in gr_handle_rename
(which is in gracl.c).
(I don't know if it is relevant, but as it was the same for both crashes
I guess there is perhaps something weird here...).
The DM patch I'm using is linux-2.4.26-rc1-devmapper-ioctl.patch.gz.
Regards,
--MiKael
P.-S.: please CC me as I'm not on this list...
reply other threads:[~2004-08-25 21:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040825210527.GK21691@lilotux.net \
--to=bmikael@lists.lilotux.net \
--cc=linux-lvm@redhat.com \
/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