linux-kernel - Re: ext3 oops with 2.4.33.3-grsec

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4539FE18.8090205@azoff.se>
Date:	Sat, 21 Oct 2006 13:01:44 +0200
From:	Torbjörn Svensson <lkml@...ff.se>
To:	Willy Tarreau <w@....eu>
Cc:	linux-kernel@...r.kernel.org, grsecurity@...ecurity.net
Subject: Re: ext3 oops with 2.4.33.3-grsec

-----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-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/