* [PATCH 1/1 linux-next] udf: return inappropriate ioctl instead of argument error
@ 2017-01-19 20:41 Fabian Frederick
2017-01-20 10:19 ` Jan Kara
0 siblings, 1 reply; 2+ messages in thread
From: Fabian Frederick @ 2017-01-19 20:41 UTC (permalink / raw)
To: Jan Kara; +Cc: linux-kernel, linux-fsdevel, fabf
Currently, lsattr for instance in udf directory gives
"udf: Invalid argument While reading flags on ..."
This patch removes argument testing and returns -ENOIOCTLCMD
when command is unknown to have more accurate message like this:
"Inappropriate ioctl for device While reading flags on ..."
If arg is NULL, we return specific operation error anyway.
Signed-off-by: Fabian Frederick <fabf@skynet.be>
---
fs/udf/file.c | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/fs/udf/file.c b/fs/udf/file.c
index dbcb3a4a..964620b 100644
--- a/fs/udf/file.c
+++ b/fs/udf/file.c
@@ -184,12 +184,6 @@ long udf_ioctl(struct file *filp, unsigned int cmd, unsigned long arg)
goto out;
}
- if (!arg) {
- udf_debug("invalid argument to udf_ioctl\n");
- result = -EINVAL;
- goto out;
- }
-
switch (cmd) {
case UDF_GETVOLIDENT:
if (copy_to_user((char __user *)arg,
@@ -220,6 +214,8 @@ long udf_ioctl(struct file *filp, unsigned int cmd, unsigned long arg)
UDF_I(inode)->i_ext.i_data,
UDF_I(inode)->i_lenEAttr) ? -EFAULT : 0;
goto out;
+ default:
+ return -ENOIOCTLCMD;
}
out:
--
2.9.3
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH 1/1 linux-next] udf: return inappropriate ioctl instead of argument error
2017-01-19 20:41 [PATCH 1/1 linux-next] udf: return inappropriate ioctl instead of argument error Fabian Frederick
@ 2017-01-20 10:19 ` Jan Kara
0 siblings, 0 replies; 2+ messages in thread
From: Jan Kara @ 2017-01-20 10:19 UTC (permalink / raw)
To: Fabian Frederick; +Cc: Jan Kara, linux-kernel, linux-fsdevel
On Thu 19-01-17 21:41:37, Fabian Frederick wrote:
> Currently, lsattr for instance in udf directory gives
> "udf: Invalid argument While reading flags on ..."
>
> This patch removes argument testing and returns -ENOIOCTLCMD
> when command is unknown to have more accurate message like this:
> "Inappropriate ioctl for device While reading flags on ..."
> If arg is NULL, we return specific operation error anyway.
OK, ENOIOCTLCMD is better than EINVAL but for the case of NULL argument for
correct ioctl command you should keep the check so that we don't fault and
kill the caller instead of returning EINVAL as we used to...
Honza
>
> Signed-off-by: Fabian Frederick <fabf@skynet.be>
> ---
> fs/udf/file.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/fs/udf/file.c b/fs/udf/file.c
> index dbcb3a4a..964620b 100644
> --- a/fs/udf/file.c
> +++ b/fs/udf/file.c
> @@ -184,12 +184,6 @@ long udf_ioctl(struct file *filp, unsigned int cmd, unsigned long arg)
> goto out;
> }
>
> - if (!arg) {
> - udf_debug("invalid argument to udf_ioctl\n");
> - result = -EINVAL;
> - goto out;
> - }
> -
> switch (cmd) {
> case UDF_GETVOLIDENT:
> if (copy_to_user((char __user *)arg,
> @@ -220,6 +214,8 @@ long udf_ioctl(struct file *filp, unsigned int cmd, unsigned long arg)
> UDF_I(inode)->i_ext.i_data,
> UDF_I(inode)->i_lenEAttr) ? -EFAULT : 0;
> goto out;
> + default:
> + return -ENOIOCTLCMD;
> }
>
> out:
> --
> 2.9.3
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-01-20 10:19 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-01-19 20:41 [PATCH 1/1 linux-next] udf: return inappropriate ioctl instead of argument error Fabian Frederick
2017-01-20 10:19 ` Jan Kara
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).