From: Pete Zaitcev <zaitcev@redhat.com>
To: greg@kroah.com
Cc: linux-kernel@vger.kernel.org, zaitcev@redhat.com
Subject: Binary sysfs blobs
Date: Tue, 11 Apr 2006 11:08:41 -0700 [thread overview]
Message-ID: <20060411110841.71390306.zaitcev@redhat.com> (raw)
Hi, Greg:
I was reviewing some patches here and noticed (yes, only now noticed) that
we have operations on binary blobs in fs/sysfs/bin.c. I thought it wasn't
part of the deal for sysfs, with one value per file and so on. I suppose
it's too late to debate now, but I have a couple of questions:
- Do you know of any conventions which allow to determine which file
is binary? Maybe the name starting with an underscore or something?
- Is there a standing policy that reading from a sysfs file is not
altering a state of the corresponding hardware? This is not related
to blobs directly, but with people passing structs now, it's tempting
to implement some extended protocols. I am concerned of stealing
network packets by accident or something.
Greetings,
-- Pete
next reply other threads:[~2006-04-11 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 18:08 Pete Zaitcev [this message]
2006-04-11 18:57 ` Binary sysfs blobs Jesse Barnes
2006-04-11 20:42 ` Greg KH
2006-04-12 10:34 ` Pete Zaitcev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060411110841.71390306.zaitcev@redhat.com \
--to=zaitcev@redhat.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox