Bug 719204 - open /proc/xen/privcmd returns EIO instead of EINVAL
Summary: open /proc/xen/privcmd returns EIO instead of EINVAL
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel-xen
Version: 5.7
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Xen Maintainance List
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-06 03:45 UTC by Caspar Zhang
Modified: 2013-07-03 07:31 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-07 07:06:06 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Caspar Zhang 2011-07-06 03:45:11 UTC
Description of problem:

in RHEL5.6 xen, when trying to read from /proc/xen/privcmd, it returned EINVAL; however it turns to be EIO in RHEL5.7. This issue is found when testing LTP/fs/proc01 test on RHEL5.7 xen kernel.

Version-Release number of selected component (if applicable):
kernel-xen-2.6.18-272.el5

How reproducible:
always

Steps to Reproduce:
1. 
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Andrew Jones 2011-07-07 07:06:06 UTC
$ grep EIO drivers/xen/privcmd/*

nothing

$ grep EINVAL drivers/xen/privcmd/*
drivers/xen/privcmd/privcmd.c:		rc = -EINVAL;
drivers/xen/privcmd/privcmd.c:			rc = -EINVAL;
drivers/xen/privcmd/privcmd.c:			return -EINVAL;
drivers/xen/privcmd/privcmd.c:			return -EINVAL;
drivers/xen/privcmd/privcmd.c:		ret = -EINVAL;

So not a privcmd issue.

I'm just going to close this as not-a-bug, because I don't want to try and figure out where it should go. It's clear the reporter needs to double check the test to know what is returning what before reopening it anyway.

Comment 4 Caspar Zhang 2011-07-08 04:25:00 UTC
Seems this bug was solved by bug 717068.


Note You need to log in before you can comment on or make changes to this bug.