From: Michael Orlitzky <michael@orlitzky.com>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Hardened meeting log 2011-03-23 20:00 UTC
Date: Tue, 29 Mar 2011 21:11:00 -0400 [thread overview]
Message-ID: <4D928324.5060904@orlitzky.com> (raw)
In-Reply-To: <4D926205.6090700@gentoo.org>
On 03/29/2011 06:49 PM, Anthony G. Basile wrote:
> On 03/29/2011 11:59 AM, Michael Orlitzky wrote:
>> On 03/29/11 07:17, Magnus Granberg wrote:
>>> [22:55:55] <blueness> HP smart array, the CCISS driver is borked on 2.6.37 and maybe 2.6.38
>>> [22:56:07] <blueness> this is a blocker to stabilizing 2.6.37 right now
>>> [22:56:25] <prometheanfire> I thought that has been known for a while now though
>>> [22:56:29] <blueness> if i can't resolve it, i'll make a patch to revert the commits that changed how the pci bus is read on those systems
>>> [22:56:48] <blueness> prometheanfire, yes, but there's some confusion about it
>>> [22:57:10] <blueness> some people think it works, i've asked chainsaw to confirm before i file the bug, he has the same systems
>>
>> I have a bunch of these too and would rather they not die after an
>> upgrade. Anything I can do to help?
>
> Yes. I've been busy, but what we should do is test hardened 2.6.37-r7
> and compare this to vanilla 2.6.37.4. If it happens on both, then we
> need to file a bug upstream while I revert the commits in .37 to the way
> the pci bus is scanned for cciss.
>
Got it. Any particular type of borkage I should be looking for?
next prev parent reply other threads:[~2011-03-30 2:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 11:17 [gentoo-hardened] Hardened meeting log 2011-03-23 20:00 UTC Magnus Granberg
2011-03-29 15:59 ` Michael Orlitzky
2011-03-29 22:49 ` Anthony G. Basile
2011-03-30 1:11 ` Michael Orlitzky [this message]
2011-03-30 11:56 ` Anthony G. Basile
2011-03-31 17:27 ` [gentoo-hardened] BFS scheduler and GRSEC/PaX patches Anthony G. Basile
2011-04-01 20:16 ` [gentoo-hardened] Hardened meeting log 2011-03-23 20:00 UTC Michael Orlitzky
2011-04-02 1:32 ` Anthony G. Basile
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=4D928324.5060904@orlitzky.com \
--to=michael@orlitzky.com \
--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