From: Andrew Patterson <andrew.patterson@hp.com>
To: linux-kernel@vger.kernel.org
Cc: linux-hotplug@vger.kernel.org
Subject: Error returns not handled correctly by sysfs.c:subsys_attr_store()
Date: Wed, 21 Nov 2007 15:16:59 -0700 [thread overview]
Message-ID: <1195683419.16019.225.camel@grinch> (raw)
The buf in fs/sysfs.c:subsys_attr_store() does not seem to be updated
correctly when returning a negative value (indicating that an error
condition has occurred) is returned. If a negative value is returned,
the next subsequent call to subsys_attr_store will have the contents of
buf appended to the previous call. Example: I have modified the
sd.c:sd_store_allow_restart to always print out the contents of the buf
and return an error using the following patch:
--- a/drivers/scsi/sd.c
+++ b/drivers/scsi/sd.c
@@ -183,6 +183,9 @@ static ssize_t sd_store_allow_restart(struct class_device *c
struct scsi_disk *sdkp = to_scsi_disk(cdev);
struct scsi_device *sdp = sdkp->device;
+ printk(KERN_ERR "buf_ptr = 0x%p, buf = %s, count = %u\n", buf, buf, coun
+ return -EINVAL;
+
if (!capable(CAP_SYS_ADMIN))
return -EACCES;
I get the following output when writing invalid values to the
allow_restart sysfs file:
# echo x > /sys/class/scsi_disk/4:0:0:0/allow_restart
bash: echo: write error: Invalid argument
# echo y > /sys/class/scsi_disk/4:0:0:0/allow_restart
bash: echo: write error: Invalid argument
# echo z > /sys/class/scsi_disk/4:0:0:0/allow_restart
bash: echo: write error: Invalid argument
And the console output shows:
buf_ptr = 0xe00001004bdb0000, buf = x
, count = 2
buf_ptr = 0xe00001004bdb0000, buf = x
, count = 2
buf_ptr = 0xe00001004bdb0000, buf = x
y
, count = 4
buf_ptr = 0xe00001004bdb0000, buf = x
y
, count = 4
buf_ptr = 0xe00001004caf0000, buf = x
y
z
, count = 6
buf_ptr = 0xe00001004caf0000, buf = x
y
z
, count = 6
and the same append problem occurs when using another sysfs file:
# echo xyzzy > /sys/class/scsi_disk/4:0:1:0/allow_restart
bash: echo: write error: Invalid argument
buf_ptr = 0xe00001004caf0000, buf = x
y
z
xyzzy
, count = 12
I found this problem in 2.6.24-rc3 and and an earlier version of 2.6.23.
This seems to work correctly on 2.6.18 (at least with the RHEL5 kernel I
did some testing with), i.e. the contents of buf from the previous
failed called are thrown away/overwritten. I looked through sysfs.c to
see if I could find anything obvious but could not see anything.
Perhaps this is handled at a higher level.
--
Andrew Patterson
Hewlett-Packard
next reply other threads:[~2007-11-21 22:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 22:16 Andrew Patterson [this message]
2007-11-27 4:31 ` Andrew Morton
2007-11-27 5:33 ` Greg KH
2007-11-27 5:38 ` Tejun Heo
2007-11-28 7:42 ` Tejun Heo
2007-11-28 19:31 ` Andrew Patterson
2007-11-28 20:05 ` Greg KH
2007-11-29 1:07 ` Tejun Heo
2007-12-03 21:15 ` Andrew Patterson
2007-12-21 20:35 ` Greg KH
2008-01-03 23:51 ` Andrew Patterson
2008-01-04 0:07 ` Tejun Heo
2008-01-04 0:17 ` Andrew Patterson
2008-01-04 0:56 ` Andrew Patterson
2008-01-04 7:30 ` Andrey Borzenkov
2008-01-07 21:13 ` Andrew Patterson
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=1195683419.16019.225.camel@grinch \
--to=andrew.patterson@hp.com \
--cc=linux-hotplug@vger.kernel.org \
--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
Powered by JetHome