From: Vikas Chaudhary <vikas.chaudhary@qlogic.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Mike Christie <michaelc@cs.wisc.edu>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Vikas Chaudhary <vikas.chaudhary@qlogic.com>,
Lalit Chandivade <lalit.chandivade@qlogic.com>,
Ravi Anand <ravi.anand@qlogic.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: Bug in sysfs bin attribute?
Date: Tue, 22 May 2012 22:38:11 -0700 [thread overview]
Message-ID: <CBE2759B.EEFF%vikas.chaudhary@qlogic.com> (raw)
We have added sysfs bin_attribute 'fw_dump' in qla4xxx driver.
Here is patch for same: -
http://marc.info/?l=linux-scsi&m=133733192809849&w=2
In this patch in function qla4_8xxx_sysfs_write_fw_dump() if we print
string coming in 'char *buf'
from sysfs attribute it contain value we echo on sysfs attribute 'fw_dump'
plus some garbage data.
If I write "5" to sysfs attribute I am getting following string in buf : -
May 18 12:08:00 magana kernel: ----------------
May 18 12:08:00 magana kernel: buf: 5
May 18 12:08:00 magana kernel: /../../host10 <-- Garbage data
May 18 12:08:00 magana kernel: ----------------
Because of this garbage data kstrtol() fails in function
qla4_8xxx_sysfs_write_fw_dump().
If we use simple_strtol() instate of kstrtol() it works well. But
simple_strtol() is deprecated
so we can't use this API.
Solution to this, for now are writing "0" at buf[1] as we are interested
only in value at buf[0].
I am interested to know if the behavior of sysfs attribute is correct or
is it an issue?
Thanks,
Vikas.
This message and any attached documents contain information from QLogic Corporation or its wholly-owned subsidiaries that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message.
next reply other threads:[~2012-05-23 5:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 5:38 Vikas Chaudhary [this message]
2012-05-23 6:17 ` gregkh
2012-05-23 8:55 ` Vikas Chaudhary
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=CBE2759B.EEFF%vikas.chaudhary@qlogic.com \
--to=vikas.chaudhary@qlogic.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=gregkh@linuxfoundation.org \
--cc=lalit.chandivade@qlogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=ravi.anand@qlogic.com \
/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