linux-kernel - Re: [PATCH 2.6.24] mm: BadRAM support for broken memory

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080302175326.GB32381@nineveh.local>
Date:	Sun, 2 Mar 2008 12:53:27 -0500
From:	Joseph Fannin <jfannin@...il.com>
To:	Rick van Rein <rick@...rein.org>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org
Subject: Re: [PATCH 2.6.24] mm: BadRAM support for broken memory

On Sun, Mar 02, 2008 at 01:42:21PM +0000, Rick van Rein wrote:
> This is the latest version of the BadRAM patch, which makes it possible to
> run Linux on broken memory.  The patch supports the use of a lesser grade
> of memory, which could be marketed more cheaply and which would thereby
> decrease the environmental stress caused by the process of (memory) chip
> manufacturing.
>
> Over the years, feedback on this patch has invariably been positive and
> enthousiastic.  The patch, even though not part of mainstream Linux, still
> managed to make lots of people happy:
>  - schools and other low-budget computer users
>  - people with partially defective RAM soldered onto laptop motherboards
>  - people with one faulty address due to wiring faults on their motherboard
>  - people who find it environmentally insane to toss out 99.99%-good hardware
>
> The patch has been well-maintained over the years, mostly by volunteers
> who keep track of kernel updates.  The submitters have changed over the years,
> but there have always been volunteers jumping in, sometimes within hours after
> a new kernel appeared, and mostly within a day.  I have processed support
> requests and used them to learn and make the patch work optimally.  It is
> obvious to me that the patch is in good demand, and I think it earns to be
> included in the mainstream kernel.
>
> The current version supports ia32 and x86_64 architectures.  Others would
> be unpractical to add on a patch outside mainstream Linux, but it ought to
> be straightforward to add support for other architectures as well.
>
> For more information, read Documentation/badram.txt or visit the homepage
> for the patch, http://rick.vanrein.org/linux/badram/

This is a great feature for those of us who value their money more
than a few hours of time as well.  :-)

I would very much like to see this patch in mainline -- I've used it
to allow use of a marginally bad RAM stick in my home
workstation/fileserver, with great results (i.e. my FS never went
belly-up).

There have been times when I was reluctant to report bugs in a BadMEM
patched kernel, due to the patching, as well as times when I would
have liked to have stuck with my distro's kernel, but couldn't, 'cause
I needed to patch BadRAM in.

I haven't used BadRAM in a minute, nor read the patch.  ISTR that one
argument that has been historically made against this sort of thing is
that it would make bug reports unreliable.  But we have the taint
mechanism now, so that shouldn't be a showstopper -- if that's the
only argument, then set a new taint flag, please.

I've added a akpm to the CC list.

--
Joseph Fannin
jfannin@...il.com

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