From: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
To: thomas@m3y3r.de
Cc: linux-kernel@vger.kernel.org, linux-nilfs@vger.kernel.org
Subject: Re: [PATCH] nilfs2: unbreak compat ioctl
Date: Thu, 10 Nov 2011 12:49:18 +0900 (JST) [thread overview]
Message-ID: <20111110.124918.255392182.ryusuke@osrg.net> (raw)
In-Reply-To: <1320697117.1396.4.camel@localhost.localdomain>
On Mon, 07 Nov 2011 21:18:37 +0100, Thomas Meyer wrote:
> I guess commit 828b1c50ae11e6dda68f8dfefe43b74c7182b157 incidentally broke
> all other compat ioctls. make them work again.
>
> Signed-off-by: Thomas Meyer <thomas@m3y3r.de>
> ---
> fs/nilfs2/ioctl.c | 2 --
> 1 files changed, 0 insertions(+), 2 deletions(-)
>
> diff --git a/fs/nilfs2/ioctl.c b/fs/nilfs2/ioctl.c
> index 41d6743..1773a98 100644
> --- a/fs/nilfs2/ioctl.c
> +++ b/fs/nilfs2/ioctl.c
> @@ -842,8 +842,6 @@ long nilfs_compat_ioctl(struct file *filp, unsigned int cmd, unsigned long arg)
> case FS_IOC32_GETVERSION:
> cmd = FS_IOC_GETVERSION;
> break;
> - default:
> - return -ENOIOCTLCMD;
> }
> return nilfs_ioctl(filp, cmd, (unsigned long)compat_ptr(arg));
> }
> --
> 1.7.7
Hi, thank you for pointing this out.
But, this patch looks to prevent compat_sys_ioctl() from handling
other compatible ioctls that compat_ioctl_check_table function
detects. For instance, fiemap (FS_IOC_FIEMAP) is handled via the
function.
I think we should only redirect own ioctl commands
(i.e. NILFS_IOCTL_xxxx) to the nilfs_ioctl() call.
Regards,
Ryusuke Konishi
next prev parent reply other threads:[~2011-11-10 3:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 20:18 [PATCH] nilfs2: unbreak compat ioctl Thomas Meyer
2011-11-10 3:49 ` Ryusuke Konishi [this message]
2011-11-13 10:32 ` Thomas Meyer
2011-11-14 9:30 ` Ryusuke Konishi
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=20111110.124918.255392182.ryusuke@osrg.net \
--to=konishi.ryusuke@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=thomas@m3y3r.de \
/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