From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Linliangjie <linliangjie@huawei.com>
Cc: shyju pv <shyju.pv@huawei.com>,
"ltp-list@lists.sourceforge.net" <ltp-list@lists.sourceforge.net>,
"Maxiansheng (Max)" <max.maxiansheng@huawei.com>,
Sanil kumar <sanil.kumar@huawei.com>
Subject: Re: [LTP] ioctl01 failed when checking the ioctl bad command return value.
Date: Thu, 01 Nov 2012 11:34:20 +0800 [thread overview]
Message-ID: <5091EDBC.4030909@cn.fujitsu.com> (raw)
In-Reply-To: <D7504F77ECABB0449431598E06DDF6E9179A600C@szxeml526-mbx.china.huawei.com>
On 11/01/2012 10:10 AM, Linliangjie wrote:
> Issue description:
> -------------------
> Kernel Version : 3.7-rc2
> System call : ioctl
> LTP Testcase : ioctl01
> LTP Version : 20120903
> Platform : x86_64 ( HP 8200 PC )
> Testcase Description : Testcase to check the errnos set by the ioctl(2) system
> call.
> Previous kernel version in which testcase passed : 3.2.9
>
> Executing log:
> -------------------------
> [root@linux-qf4g]-[/tmp/ltp/ltp/testcases/bin]
> (0)# ./ioctl01 -D /dev/tty
> ioctl01 1 TPASS : failed as expected: TEST_ERRNO=EBADF(9): Bad file
> descriptor
> ioctl01 2 TPASS : failed as expected: TEST_ERRNO=EFAULT(14): Bad address
> ioctl01 3 TFAIL : failed unexpectedly; expected 22 - Invalid argument:
> TEST_ERRNO=ENOTTY(25): Inappropriate ioctl for device
> ioctl01 4 TPASS : failed as expected: TEST_ERRNO=ENOTTY(25):
> Inappropriate ioctl for device
> ioctl01 5 TPASS : failed as expected: TEST_ERRNO=EFAULT(14): Bad address
> -------------------------
> The return value of the code is expected to be 22 but 24 is returned and
> hence the LTP test failed.
>
>>From v3.2.9, kernel has changed the return value for bad command.
> The patch commit no:07d106d0a33d6063d2061305903deb02489eba20
Yes, you are right, but you didn't find the real effective patch,
the real effective patch is
commit bbb63c514a3464342967237a51a21ea8f61ab951
Author: Wanlong Gao <gaowanlong@cn.fujitsu.com>
Date: Mon Aug 27 15:23:12 2012 +0800
drivers:tty:fix up ENOIOCTLCMD error handling
At commit 07d106d0, Linus pointed out that ENOIOCTLCMD should be
translated as ENOTTY to user mode.
For example:
fd = open("/dev/tty", O_RDWR);
ioctl(fd, -1, &argp);
then the errno should be ENOTTY but not EINVAL.
Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
Acked-by: Alan Cox <alan@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
It's a kernel change, so I will make a patch to fix this LTP test case.
Thank you very much for reporting this. ;)
And you *Huawei* guys are very welcome to the Open Source community. :-)
Regards,
Wanlong Gao
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2012-11-01 3:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 2:10 [LTP] ioctl01 failed when checking the ioctl bad command return value Linliangjie
2012-11-01 3:34 ` Wanlong Gao [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=5091EDBC.4030909@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=linliangjie@huawei.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=max.maxiansheng@huawei.com \
--cc=sanil.kumar@huawei.com \
--cc=shyju.pv@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.