From: "Hans-Jürgen Koch" <hjk@linutronix.de>
To: linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: UIO sysfs attributes broken in 2.6.25-rc1
Date: Wed, 13 Feb 2008 18:03:04 +0100 [thread overview]
Message-ID: <20080213180304.4ffa81e9@dilbert.local> (raw)
In 2.6.25-rc1, there's a strange effect:
Although the map attributes "addr" and "size" show up correctly:
-r--r--r-- 1 root root 4096 2008-02-13 17:49 addr
-r--r--r-- 1 root root 4096 2008-02-13 17:49 size
you cannot access them, not even as root. Something like "cat addr"
fails with a no-permission-error. It works fine in 2.6.24-rc8.
This is probably related to this patch:
http://lkml.org/lkml/2008/1/25/149
Unfortunately, I signed-off that one, too... I checked if all sysfs
files appear, but didn't try to access them. Sorry.
Greg, any ideas?
Thanks,
Hans
next reply other threads:[~2008-02-13 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 17:03 Hans-Jürgen Koch [this message]
2008-02-13 17:33 ` UIO sysfs attributes broken in 2.6.25-rc1 Greg KH
2008-02-19 9:55 ` [PATCH] UIO: introduce sysfs_ops for map_attr_ktype Brandon Philips
2008-02-19 12:12 ` Hans-Jürgen Koch
2008-02-20 6:54 ` Greg KH
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=20080213180304.4ffa81e9@dilbert.local \
--to=hjk@linutronix.de \
--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