| 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
| ||
|
Date: Wed, 9 May 2012 17:01:26 -0700 From: Greg KH <greg@...ah.com> To: Evgeniy Polyakov <zbr@...emap.net> Cc: Markus Franke <markus.franke@...02.tu-chemnitz.de>, Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org Subject: Re: [PATCH] w1: Add 1-wire slave device driver for DS28E04-100 On Thu, May 10, 2012 at 03:57:23AM +0400, Evgeniy Polyakov wrote: > On Thu, May 10, 2012 at 12:37:56AM +0200, Markus Franke (markus.franke@...02.tu-chemnitz.de) wrote: > > Well, the data read/written through this file is actually directly > > "passed" on to the device. There are two bits which reflect the current > > state of the PIO pins of the DS28E04. However, I must admit that this > > could also be implemented as regular sysfs attributes. > > Greg, could you please describe what is exactly wrong with binary sysfs > file? Or am I missing that it is not usual sysfs file but some special > stuff? Binary sysfs files should be "pass through" only, the kernel should not touch the data involved in them at all, it is a pipe directly from the kernel to userspace for binary blob data, like firmware images. You should never do any processing of any binary file data at all in the kernel. Hope this helps, greg k-h -- 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/
Powered by blists - more mailing lists