From: Goffredo Baroncelli <kreijack@gmail.com>
To: Jeff Liu <jeff.liu@oracle.com>
Cc: linux-btrfs@vger.kernel.org, anand.jain@oracle.com,
miaox@cn.fujitsu.com, dsterba@suse.cz,
Stefan Behrens <sbehrens@giantdisaster.de>
Subject: Re: [RFC PATCH v7 1/2] Btrfs: Add a new ioctl to get the label of a mounted file system
Date: Mon, 24 Dec 2012 14:46:52 +0100 [thread overview]
Message-ID: <50D85CCC.5090204@gmail.com> (raw)
In-Reply-To: <50D80D5C.2060306@oracle.com>
Hi Jeff,
On 12/24/2012 09:07 AM, Jeff Liu wrote:
> On 12/22/2012 01:36 AM, Goffredo Baroncelli wrote:
>> On 12/21/2012 07:42 AM, Jeff Liu wrote:
[...]
>>> I don't think we should replace strlen() with strnlen() since it's
>>> totally wrong if the length of label is more than BTRFS_LABEL_SIZE -1,
>>> we can not just truncating the label and return it in this case.
>>
>> This for me is sufficient, or we could copy all the label buffer,
>> without further check:
>>
>> copy_to_user(arg, label, BTRFS_LABEL_SIZE)
> That sounds ok to me, but it's better to limit the length to be
> 'BTRFS_LABEL_SIZE - 1' bytes, or else, it would copy 256 bytes back to
> the user space if the label length is beyond or equal to the array limits.
Sorry I don't understand your reply. The ioctl has as argument an array
of BTRFS_LABEL_SIZE characters, so it should not be any problem of page
fault (with the exception of an user who passes a shorter array). So it
wouldn't be any problem to copy
BTRFS_LABEL_SIZE character, or I am missing something ?
The question is another. Is a kernel responsibility to assure that the
returned string is zero terminated ? If yes (and I think so) we should
truncate the string before the copy:
label[BTRFS_LABEL_SIZE-1] = 0;
copy_to_user(arg, label, BTRFS_LABEL_SIZE);
>>
>>
>>> Add BUG_ON(strlen(label) > BTRFS_LABEL_SIZE - 1) is reasonable instead.
>>
>> I agree with Stefan, this is not a correct use of BUG_ON; a warning is
>> sufficient (there is un-correct data read from disk).
> Maybe like following?
>
> size_t len = strlen(label);
If label (who is an array read from the disk) is not zero terminated,
this would lead to a possible page fault. I suggest to use strnlen() or
similar.
>
> if (len > BTRFS_LABEL_SIZE - 1) {
> WARN(1, "btrfs: device label has weird length %zu bytes, "
> "it will be truncated to %d bytes.\n",
> len, BTRFS_LABEL_SIZE - 1);
>
> len = BTRFS_LABEL_SIZE - 1;
> }
As message I suggest:
WARN(1, "btrfs: device label is not zero terminated, it will be
truncated to %d bytes.\n",
BTRFS_LABEL-1 );
NOTE: it is suggested to not span the string on more lines, to help
searching in the source a messages with grep. It is an exception of the
rule of the max 80 columns text width.
Happy Christmas you too
GB
>
> I'll post a new patch with those changes if no other objections.
>
> Happy Christmas.
> -Jeff
>>
>>>
>>> Thanks,
>>> -Jeff
>>>>
>>>>> + mutex_unlock(&root->fs_info->volume_mutex);
>>>>> +
>>>>> + return ret ? -EFAULT : 0;
>>>>> +}
>>>>> +
>>>>> long btrfs_ioctl(struct file *file, unsigned int
>>>>> cmd, unsigned long arg)
>>>>> {
>>>>> @@ -3797,6 +3810,8 @@ long btrfs_ioctl(struct file *file, unsigned int
>>>>> return btrfs_ioctl_qgroup_create(root, argp);
>>>>> case BTRFS_IOC_QGROUP_LIMIT:
>>>>> return btrfs_ioctl_qgroup_limit(root, argp);
>>>>> + case BTRFS_IOC_GET_FSLABEL:
>>>>> + return btrfs_ioctl_get_fslabel(file, argp);
>>>>> }
>>>>>
>>>>> return -ENOTTY;
>>>>> diff --git a/fs/btrfs/ioctl.h b/fs/btrfs/ioctl.h
>>>>> index 731e287..5b2cbef 100644
>>>>> --- a/fs/btrfs/ioctl.h
>>>>> +++ b/fs/btrfs/ioctl.h
>>>>> @@ -451,6 +451,8 @@ struct btrfs_ioctl_send_args {
>>>>> struct btrfs_ioctl_qgroup_create_args)
>>>>> #define BTRFS_IOC_QGROUP_LIMIT _IOR(BTRFS_IOCTL_MAGIC, 43, \
>>>>> struct btrfs_ioctl_qgroup_limit_args)
>>>>> +#define BTRFS_IOC_GET_FSLABEL _IOR(BTRFS_IOCTL_MAGIC, 49, \
>>>>> + char[BTRFS_LABEL_SIZE])
>>>>> #define BTRFS_IOC_GET_DEV_STATS _IOWR(BTRFS_IOCTL_MAGIC, 52, \
>>>>> struct btrfs_ioctl_get_dev_stats)
>>>>> #endif
>>>>
>>>>
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>>
>>
>
>
--
gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2012-12-24 13:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 8:43 [RFC PATCH v7 0/2] Btrfs: get/set label of a mounted file system Jeff Liu
2012-12-20 8:43 ` [RFC PATCH v7 1/2] Btrfs: Add a new ioctl to get the " Jeff Liu
2012-12-20 20:18 ` Goffredo Baroncelli
2012-12-21 6:42 ` Jeff Liu
2012-12-21 8:50 ` Stefan Behrens
2012-12-21 17:36 ` Goffredo Baroncelli
2012-12-24 8:07 ` Jeff Liu
2012-12-24 13:46 ` Goffredo Baroncelli [this message]
2012-12-24 15:10 ` Jeff Liu
2012-12-20 8:43 ` [RFC PATCH v7 2/2] Btrfs: Add a new ioctl to set/change " Jeff Liu
2012-12-20 20:19 ` Goffredo Baroncelli
2012-12-27 17:34 ` David Sterba
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=50D85CCC.5090204@gmail.com \
--to=kreijack@gmail.com \
--cc=anand.jain@oracle.com \
--cc=dsterba@suse.cz \
--cc=jeff.liu@oracle.com \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=miaox@cn.fujitsu.com \
--cc=sbehrens@giantdisaster.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;
as well as URLs for NNTP newsgroup(s).