From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Chen Guanqiao <chen.chenchacha@foxmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: fat: add ioctl to modify fat filesystem volume label
Date: Thu, 21 Dec 2017 00:49:13 +0900 [thread overview]
Message-ID: <87k1xhh01y.fsf@mail.parknet.co.jp> (raw)
In-Reply-To: <20171220140547.5173-1-chen.chenchacha@foxmail.com> (Chen Guanqiao's message of "Wed, 20 Dec 2017 22:05:47 +0800")
Chen Guanqiao <chen.chenchacha@foxmail.com> writes:
> The FAT filesystem volume label can be read with FAT_IOCTL_GET_VOLUME_LABEL
> and written with FAT_IOCTL_SET_VOLUME_LABEL.
Those vol_label should be matching with volume label in root directory,
right? So I think handling only boot sector's vol_label would not work
as expected.
> +static int fat_ioctl_get_volume_label(struct inode *inode,
> + u32 __user *user_attr)
Maybe you are using non-8 tab size, and so over 80 column.
> +{
> + struct msdos_sb_info *sbi = MSDOS_SB(inode->i_sb);
> + u8 __user *vol_label = (u8 __user *)user_attr;
This should not use strange cast (u32 => u8), instead caller should cast
to proper one.
> + return copy_to_user(vol_label, sbi->vol_label, sizeof(sbi->vol_label));
> +}
Returning result of copy_to_user() is strange. Probably, it should
return 0 or -EFAULT.
> +static int fat_ioctl_set_volume_label(struct inode *inode,
> + u32 __user *user_attr)
same indent issue.
> +{
> + struct buffer_head *bh;
> + struct fat_boot_sector *b;
> + struct msdos_sb_info *sbi = MSDOS_SB(inode->i_sb);
> + u8 __user *vol_label = (u8 __user *)user_attr;
> + u8 label[11];
It should not allow to change for normal user that having only read access.
> + if (copy_from_user(label, vol_label, sizeof(label)))
> + return -EFAULT;
It should check invalid label early (e.g. lower case chars, invalid
chars, etc.).
> + if (sb_rdonly(inode->i_sb))
> + return -EFAULT;
-EROFS
> + bh = sb_bread(inode->i_sb, 0);
> + if (bh == NULL) {
> + fat_msg(inode->i_sb, KERN_ERR,
> + "unable to read boot sector to write volume label");
indent issue.
> + return -EFAULT;
> + }
It should take lock to prevent race.
> + b = (struct fat_boot_sector *) bh->b_data;
> +
> + if (sbi->fat_bits == 32)
> + memcpy(b->fat32.vol_label, label, sizeof(label));
> + else
> + memcpy(b->fat16.vol_label, label, sizeof(label));
> +
> + mark_buffer_dirty(bh);
> + sync_dirty_buffer(bh);
It should check I/O error.
> long fat_generic_ioctl(struct file *filp, unsigned int cmd, unsigned long arg)
> {
u8 __user *user_vol_label = (u8 __user *)arg;
> + case FAT_IOCTL_GET_VOLUME_LABEL:
> + return fat_ioctl_get_volume_label(inode, user_attr);
> + case FAT_IOCTL_SET_VOLUME_LABEL:
> + return fat_ioctl_set_volume_label(inode, user_attr);
s/user_attr/user_vol_label/
> diff --git a/fs/fat/inode.c b/fs/fat/inode.c
> index 20a0a89eaca5..9991500c98af 100644
> --- a/fs/fat/inode.c
> +++ b/fs/fat/inode.c
> @@ -45,12 +45,14 @@ struct fat_bios_param_block {
>
> u8 fat16_state;
> u32 fat16_vol_id;
> + u8 fat16_vol_label[11];
> + u8 fat32_vol_label[11];
indent.
> +#define FAT_IOCTL_SET_VOLUME_LABEL _IOR('r', 0x15, __u8[11])
_IOW
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
prev parent reply other threads:[~2017-12-20 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 14:05 Chen Guanqiao
2017-12-20 15:49 ` OGAWA Hirofumi [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=87k1xhh01y.fsf@mail.parknet.co.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=chen.chenchacha@foxmail.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®