From: Shi Weihua <shiwh@cn.fujitsu.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [BUG?] proc01: read /proc/acpi/event failed if acpi daemon stopped
Date: Tue, 23 Mar 2010 13:22:40 +0800 [thread overview]
Message-ID: <4BA85020.9040202@cn.fujitsu.com> (raw)
In-Reply-To: <364299f41003222057i6caa2cc8g6b1786f3cee86a74@mail.gmail.com>
at 2010-3-23 11:57, Garrett Cooper wrote:
> On Mon, Mar 22, 2010 at 3:06 AM, Shi Weihua <shiwh@cn.fujitsu.com> wrote:
>> Hi Garrett
>>
>> at 2010-3-13 15:13, Garrett Cooper wrote:
>>> On Fri, Mar 12, 2010 at 10:27 PM, Garrett Cooper <yanegomi@gmail.com> wrote:
>>>> On Fri, Mar 12, 2010 at 7:49 PM, Shi Weihua <shiwh@cn.fujitsu.com> wrote:
>>>>> An error message occured when i tested proc01.
>>>>> ---------
>>>>> proc01 1 TFAIL : read failed: /proc/acpi/event: errno=EAGAIN(11): Resource temporarily unavailable
>>>>> ---------
>>>>>
>>>>> If "service acpid start", this message will be turned to:
>>>>> ---------
>>>>> proc01 0 TINFO : /proc/acpi/event: known issue: errno=EBUSY(16): Device or resource busy
>>>>> ---------
>>>>>
>>>>> I think we should to add a check of acpi daemon's status in testcases/kernel/fs/proc/proc01.c.
>>>>
>>>> No, that's making things too complicated and won't scale as every
>>>> distro has developed a different means for specifying the status for a
>>>> service. Why not just add EAGAIN for that /proc node?
>>>
>>> And FWIW the error condition is correct in my opinion if kernel
>>> acpi hasn't been enabled, which was the case here.
>>
>> I think we should to give a warning message to LTP users.
>> How do you think the following patch?
>>
>> diff --git a/testcases/kernel/fs/proc/proc01.c b/testcases/kernel/fs/proc/proc01.c
>> index 2d4a5fd..62d44b1 100644
>> --- a/testcases/kernel/fs/proc/proc01.c
>> +++ b/testcases/kernel/fs/proc/proc01.c
>> @@ -101,6 +101,7 @@ const Mapping known_issues[] = {
>> {"read", "/proc/fs/nfsd/filehandle", EINVAL},
>> {"read", "/proc/fs/nfsd/.getfs", EINVAL},
>> {"read", "/proc/fs/nfsd/.getfd", EINVAL},
>> + {"read", "/proc/acpi/event", EAGAIN}, //EAGAIN will be returned if acpi daemon disabled
>> {"", "", 0}
>> };
>
> Looks good minus the C++ style comment ;).
ok, let's use C style comment.
diff --git a/testcases/kernel/fs/proc/proc01.c b/testcases/kernel/fs/proc/proc01.c
index 2d4a5fd..355b7dd 100644
--- a/testcases/kernel/fs/proc/proc01.c
+++ b/testcases/kernel/fs/proc/proc01.c
@@ -101,6 +101,7 @@ const Mapping known_issues[] = {
{"read", "/proc/fs/nfsd/filehandle", EINVAL},
{"read", "/proc/fs/nfsd/.getfs", EINVAL},
{"read", "/proc/fs/nfsd/.getfd", EINVAL},
+ {"read", "/proc/acpi/event", EAGAIN}, /* EAGAIN will be returned if acpi daemon disabled */
{"", "", 0}
};
> Thanks again!
> -Garrett
>
>
--
Shi Weihua
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2010-03-23 5:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-13 3:49 [LTP] [BUG?] proc01: read /proc/acpi/event failed if acpi daemon stopped Shi Weihua
2010-03-13 6:27 ` Garrett Cooper
2010-03-13 7:13 ` Garrett Cooper
2010-03-22 10:06 ` Shi Weihua
2010-03-23 3:57 ` Garrett Cooper
2010-03-23 5:22 ` Shi Weihua [this message]
2010-03-23 16:44 ` Garrett Cooper
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=4BA85020.9040202@cn.fujitsu.com \
--to=shiwh@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=yanegomi@gmail.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