public inbox for ntfs3@lists.linux.dev
 help / color / mirror / Atom feed
From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Kari Argillander <kari.argillander@gmail.com>, <ntfs3@lists.linux.dev>
Cc: linux-kernel@vger.kernel.org, "Pali Rohár" <pali@kernel.org>
Subject: Re: [PATCH] fs/ntfs3: Remove fat ioctl's from ntfs3 driver for now
Date: Tue, 31 Aug 2021 19:19:41 +0300	[thread overview]
Message-ID: <ca096313-ddb6-6897-67a6-3f0d45deefce@paragon-software.com> (raw)
In-Reply-To: <20210824182020.1007329-1-kari.argillander@gmail.com>



On 24.08.2021 21:20, Kari Argillander wrote:
> For some reason we have FAT ioctl calls. Even old ntfs driver did not
> use these. We should not use these because it his hard to get things out
> of kernel when they are upstream. That's why we remove these for now.
> 
> More discussion is needed what ioctl should be implemented and what is
> important.
> 
> Signed-off-by: Kari Argillander <kari.argillander@gmail.com>
> ---
> Earlier disgussion with Pali can be founded here:
> lore.kernel.org/linux-fsdevel/20210824113304.eabzy7ulbuouzlac@pali/
> ---
>  fs/ntfs3/file.c | 8 --------
>  1 file changed, 8 deletions(-)
> 
> diff --git a/fs/ntfs3/file.c b/fs/ntfs3/file.c
> index 59344985c2e8..819afc4c902b 100644
> --- a/fs/ntfs3/file.c
> +++ b/fs/ntfs3/file.c
> @@ -10,7 +10,6 @@
>  #include <linux/compat.h>
>  #include <linux/falloc.h>
>  #include <linux/fiemap.h>
> -#include <linux/msdos_fs.h> /* FAT_IOCTL_XXX */
>  #include <linux/nls.h>
>  
>  #include "debug.h"
> @@ -50,15 +49,8 @@ static long ntfs_ioctl(struct file *filp, u32 cmd, unsigned long arg)
>  {
>  	struct inode *inode = file_inode(filp);
>  	struct ntfs_sb_info *sbi = inode->i_sb->s_fs_info;
> -	u32 __user *user_attr = (u32 __user *)arg;
>  
>  	switch (cmd) {
> -	case FAT_IOCTL_GET_ATTRIBUTES:
> -		return put_user(le32_to_cpu(ntfs_i(inode)->std_fa), user_attr);
> -
> -	case FAT_IOCTL_GET_VOLUME_ID:
> -		return put_user(sbi->volume.ser_num, user_attr);
> -
>  	case FITRIM:
>  		return ntfs_ioctl_fitrim(sbi, arg);
>  	}
> 

Hi, Kari!

Applied, thanks.

Best regards.

      reply	other threads:[~2021-08-31 16:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-24 18:20 [PATCH] fs/ntfs3: Remove fat ioctl's from ntfs3 driver for now Kari Argillander
2021-08-31 16:19 ` Konstantin Komarov [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=ca096313-ddb6-6897-67a6-3f0d45deefce@paragon-software.com \
    --to=almaz.alexandrovich@paragon-software.com \
    --cc=kari.argillander@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ntfs3@lists.linux.dev \
    --cc=pali@kernel.org \
    /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