| 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 20:43:48 -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 04:43:50AM +0400, Evgeniy Polyakov wrote: > On Wed, May 09, 2012 at 05:01:26PM -0700, Greg KH (greg@...ah.com) wrote: > > 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. > > And if some of the data should be somehow changed, what interfact should > be used? Also, Markus, does DS28E04 change written/read data when doing > IO? > > I must admit, I never heared that binary sysfs files have to follow this > constraint. For some reason I thought I had documented it years ago, but in digging through the Documentation directory, I don't see it anywhere, sorry about that. I'll add it to my ever-growing TODO list... thanks, 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