> When I run ltp aio test case, for the operation OCB_CMD_FDSYNC and
> IOCB_CMD_FSYNC, io_submit returns -1 and errno is EINVAL, perror's
> output is "Invalid arguments", from the user's perspective, the
> arguments are valid and the kernel also know it and progress the
> process to file operation of the filesystem actually, so I think
> ENOTSUP is more appropriate. Note ENOTSUP in the user space
> corresponds to EOPNOTSUPP in the kernel mode. For ENOTSUP, perror's
> output is "Function isn't implemented", obviously, it is a reasonable
> explanation about the execution error and not ambiguous.
This might have been a convincing argument when the interface was first
being written, but now we have to take into account that changing the
interface can break existing users.
That you prefer EOPNOTSUPP is not a compelling reason to break existing
setups, sorry.
- z
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
