linux-kernel - Re: [RFC] BadRAM still not ready for inclusion ? (was: Re: Free Linux Driver Development!)

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: <75b66ecd0703060923yc73b796w3aae193ed5f8d9ee@mail.gmail.com>
Date:	Tue, 6 Mar 2007 12:23:21 -0500
From:	"Lee Revell" <rlrevell@...-job.com>
To:	"devzero@....de" <devzero@....de>
Cc:	linux-kernel@...r.kernel.org, greg@...ah.com, pavel@...e.cz
Subject: Re: [RFC] BadRAM still not ready for inclusion ? (was: Re: Free Linux Driver Development!)

On 3/4/07, devzero@....de <devzero@....de> wrote:
> It seems, that BadRAM is not being maintained very actively and the original author doesn`t seem to have the time pushing it into mainline, but i know it's actively being used by more then just a handful of people. Unfortunately there is no mailinglist to approve this and some "central point of communication" besides Rick van Rein doesn't seem to exist. There is a fork named BadMEM at http://sourceforge.net/projects/badmem, Memtest86 also supporting BadRAM and i have seen LOTs of discussion about BadRAM on the net. Most of that discussion was due to problems getting it run with Kernel XYZ.
>
> Basically, this feature is a matter of adding/modifying 200 lines of code, so iŽm even more wondering, why it exists for more than 7 years and nothing happening here.

Because most kernel developers don't have time to scour the net for
random kernel patches and pull them.  If you have a useful patch you
want merged it's up to you to push it.

What's so hard about submitting a 200 line patch to LKML?

Lee
-
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/