From: "Torbjörn Svensson" <lkml@azoff.se>
To: Willy Tarreau <w@1wt.eu>
Cc: linux-kernel@vger.kernel.org, grsecurity@grsecurity.net
Subject: Re: ext3 oops with 2.4.33.3-grsec
Date: Sat, 21 Oct 2006 13:01:44 +0200 [thread overview]
Message-ID: <4539FE18.8090205@azoff.se> (raw)
In-Reply-To: <20061021071138.GA1709@1wt.eu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello!
Willy Tarreau wrote:
> I see nothing between 2.4.33 and 2.4.33.3 which affects ext3 in any way.
> The "ud2a" you see in the decoded oops is a call to 'BUG()'. The only
> one I find in ext3 is in ext3_write_super() which is not called from
> any function in your trace. I do not notice any other relevant ones in
> inline functions included from other files. Could you check if the
> grsec patch you use changes anything in fs/ext3/super.c ? It will make
> the debugging easier.
No, nothing. I have put the grsec-patch I used on my httpd[0]. Could I
have got my journal corupted in someway during the random reboots? Could
it help to recreate a journal and if so, how do I do that?
[0]
http://www.azoff.se/error/debian/oops/grsecurity-2.1.9-2.4.33.3-200609031224.patch.gz
- --
> Torbjörn Svensson <lkml (at) azoff (dot) se>
> Please CC me as I am not subscribed to the list!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFOf4TeY7jmtvbDP0RAuoiAKCbX3uoh37CM5+PYE8pBXcnYA6hUgCfZnB3
guUbELQofgZwRrawrbrsCKE=
=WJeZ
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2006-10-21 11:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 15:50 ext3 oops with 2.4.33.3-grsec Torbjörn Svensson
2006-10-21 7:11 ` Willy Tarreau
2006-10-21 11:01 ` Torbjörn Svensson [this message]
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=4539FE18.8090205@azoff.se \
--to=lkml@azoff.se \
--cc=grsecurity@grsecurity.net \
--cc=linux-kernel@vger.kernel.org \
--cc=w@1wt.eu \
/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.