linux-kernel - Re: [PATCH] mtd: Add simple read disturb test

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]

Date:	Thu, 2 Apr 2015 09:04:51 -0700
From:	Brian Norris <computersforpeace@...il.com>
To:	Richard Weinberger <richard@....at>
Cc:	dwmw2@...radead.org, linux-mtd@...ts.infradead.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mtd: Add simple read disturb test

On Thu, Apr 02, 2015 at 04:13:46PM +0200, Richard Weinberger wrote:
> This simple MTD tests allows the user to see when read disturb happens.
> By reading blocks over and over it reports flipped bits.
> Currently it reports only flipped bits of the worst page of a block.
> If within block X page P1 has 3 bit flips and P6 4, it will report 4.
> By default every 50th block is read.

Didn't read through this much yet, but why do we need another in-kernel
test that coul (AFAICT) be easily replicated in userspace? The same goes
for several of the other tests, I think, actually. But at least with
those, we have a history of keeping them around, so it's not too much
burden [1].

Brian

[1] Although there are some latent issues in these tests that are still
getting get worked out (e.g., bad handling of 64-bit casting; too large
of stacks; uninterruptibility). The latter two would not even exist if
we were in user space.
--
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/