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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 1 Apr 2014 21:27:47 +0400
From:	Konstantin Khlebnikov <>
To:	One Thousand Gnomes <>
Cc:	"" <>,
	Linux Kernel Mailing List <>,
	Hugh Dickins <>,
	Yury Gribov <>,
	Alexandr Andreev <>,
	Vassili Karpov <>,
	Andrew Morton <>,
	"Kirill A. Shutemov" <>
Subject: Re: [PATCH RFC] drivers/char/mem: byte generating devices and
 poisoned mappings

On Tue, Apr 1, 2014 at 8:59 PM, One Thousand Gnomes
<> wrote:
> On Tue, 01 Apr 2014 01:16:07 +0400
> Konstantin Khlebnikov <> wrote:
>> This patch adds 256 virtual character devices: /dev/byte0, ..., /dev/byte255.
>> Each works like /dev/zero but generates memory filled with particular byte.
> More kernel code for an ultra-obscure corner case that can be done in
> user space
> I don't see the point

True. That was a long-planned joke.
But at the final moment I've found practical usage for it and overall
design became not such funny.

Currently I'm thinking about single-device model proposed by Kirill.

Let's call it /dev/poison. Application can open it, write a poison (up
to a page size) and after that this instance will generate pages
filled with this pattern. I don't see how this can be done in
userspace without major memory/cpu overhead caused by initial memset.

Default poison might be for example 0xff, so it still will be useful for 'dd'.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists