linux-kernel - Re: [PATCH] w1: Add 1-wire slave device driver for DS28E04-100

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120510004350.GA8362@ioremap.net>
Date:	Thu, 10 May 2012 04:43:50 +0400
From:	Evgeniy Polyakov <zbr@...emap.net>
To:	Greg KH <greg@...ah.com>
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 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.

-- 
	Evgeniy Polyakov
--
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/