From: Andi Kleen <andi@firstfloor.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-scsi@vger.kernel.org, bugme-daemon@bugzilla.kernel.org,
cijoml@volny.cz
Subject: Re: [Bugme-new] [Bug 10915] New: echo min_power > /sys/class/scsi_host/host0/active_mode causes problem
Date: Mon, 16 Jun 2008 14:48:20 +0200 [thread overview]
Message-ID: <87wskpwnor.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1213581610.3517.44.camel@localhost.localdomain> (James Bottomley's message of "Sun, 15 Jun 2008 21:00:10 -0500")
James Bottomley <James.Bottomley@HansenPartnership.com> writes:
>
> Um ... actually, maybe not. The active_mode file is read only (it has a
> NULL store method). It's designed to show what mode the host is
> activated in "initiator", "target" (or both or unknown). If echoing
> something to a read only sysfs file with no actual store method is
> causing this behaviour, the root cause has to be somewhere in sysfs.
>
> However, since the file has nothing to do with power saving ... unless
> some driver I can't find is trying to duplicate it, so there's no reason
> to try to echo "min_power" to it, so some of the details on this report
> might bear further investigation ...
I remember hitting something like this in the past when write() returned 0.
Some versions of echo loop in this case.
-Andi
prev parent reply other threads:[~2008-06-16 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10915-10286@http.bugzilla.kernel.org/>
2008-06-16 1:01 ` [Bugme-new] [Bug 10915] New: echo min_power > /sys/class/scsi_host/host0/active_mode causes problem Andrew Morton
2008-06-16 2:00 ` James Bottomley
2008-06-16 4:51 ` FUJITA Tomonori
2008-06-16 12:48 ` Andi Kleen [this message]
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=87wskpwnor.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=cijoml@volny.cz \
--cc=linux-scsi@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