From: "\"Tóth Attila\"" <atoth@atoth.sote.hu>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Disappearing root on 2.6.36-hardened-r6 upgrade
Date: Sun, 26 Dec 2010 19:59:49 +0100 [thread overview]
Message-ID: <0a9a7e024c2ba50c529006d9805e8ca8.squirrel@atoth.sote.hu> (raw)
In-Reply-To: <4D170EDE.15195.3043ADB6@pageexec.freemail.hu>
[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]
I don't know if it is related or not. I don't use ext4 and have no
symptoms of disappearing root. I attach a photo taken using a recent
kernel. The latest crashes I've experienced for the past few months
prevented syncing, so didn't get logged. The other screen capture is
older, may not be relevant nowdays.
Thx:
Dw.
--
dr Tóth Attila, Radiológus, 06-20-825-8057
Attila Toth MD, Radiologist, +36-20-825-8057
2010.December 26.(V) 09:46 időpontban pageexec@freemail.hu ezt írta:
> On 26 Dec 2010 at 1:59, Michael Orlitzky wrote:
>
>> I've got (at least) two servers that lose their root partition after
>> this upgrade. One of them has an HP cciss SCSI RAID controller; the
>> other has a single IDE hard drive. Assuming the problem is something
>> common, I'll stick to describing the one with the array for now.
>
> which grsec is this ebuild based on? my guess is that it's a recent
> PaX/UDEREF
> hardening that's causing this and should be mostly fixed now except for
> the
> IP checksum code fix which i'll release soon. in the meantime you can
> disable
> UDEREF. if you don't have it enabled then i don't know what it is, we'll
> need
> more debugging, let me know.
>
>
[-- Attachment #2: DSCN1253.jpg --]
[-- Type: image/jpeg, Size: 688213 bytes --]
[-- Attachment #3: DSCN1247.jpg --]
[-- Type: image/jpeg, Size: 674493 bytes --]
next prev parent reply other threads:[~2010-12-26 19:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-26 6:59 [gentoo-hardened] Disappearing root on 2.6.36-hardened-r6 upgrade Michael Orlitzky
2010-12-26 8:46 ` pageexec
2010-12-26 17:06 ` Michael Orlitzky
2010-12-26 17:57 ` pageexec
2010-12-26 19:09 ` Michael Orlitzky
2010-12-26 20:00 ` pageexec
2010-12-26 23:03 ` klondike
2010-12-27 0:05 ` klondike
2010-12-29 11:36 ` pageexec
2010-12-27 19:49 ` Michael Orlitzky
2010-12-26 19:31 ` Michael Orlitzky
2010-12-26 17:31 ` Anthony G. Basile
2010-12-26 18:01 ` Anthony G. Basile
2010-12-26 18:59 ` "Tóth Attila" [this message]
2010-12-26 20:06 ` pageexec
2010-12-26 23:01 ` klondike
2010-12-30 19:29 ` "Tóth Attila"
2010-12-30 20:35 ` pageexec
2010-12-30 23:16 ` "Tóth Attila"
2011-01-04 13:52 ` "Tóth Attila"
2011-01-04 16:46 ` pageexec
2011-01-04 18:38 ` "Tóth Attila"
2011-01-04 18:18 ` pageexec
2011-01-09 14:55 ` "Tóth Attila"
2011-01-09 22:20 ` Alex Efros
2011-01-10 0:39 ` "Tóth Attila"
2011-01-04 13:52 ` "Tóth Attila"
2011-01-04 13:16 ` pageexec
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=0a9a7e024c2ba50c529006d9805e8ca8.squirrel@atoth.sote.hu \
--to=atoth@atoth.sote.hu \
--cc=gentoo-hardened@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox