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: <20080302174235.GA26902@phantom.vanrein.org>
Date:	Sun, 2 Mar 2008 17:42:35 +0000
From:	Rick van Rein <rick@...rein.org>
To:	KOSAKI Motohiro <m-kosaki@...es.dti.ne.jp>
Cc:	Rick van Rein <rick@...rein.org>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2.6.24] mm: BadRAM support for broken memory

Hello Kosaki,

> in general,
> Agreed with we need bad memory treatness.

Glad to hear that.

> >  +#define PG_badram              20      /* BadRam page */
> 
> some architecture use PG_reserved for treat bad memory.
> Why do you want introduce new page flag?

It is clearer to properly name a flag, I suppose.
Is the use that you are mentioning the intended, and only use of the flag?
If not, I think it is clearer to use a separate flag instead of overloading
one.

> for show_mem() improvement?

For code clarity.


Thanks,
 -Rick
--
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/