btrfs: usage error should not be logged into system log
I have an opinion that system logs /var/log/messages are valuable info to investigate the real system issues at the data center. People handling data center issues do spend a lot time and efforts analyzing messages files. Having usage error logged into /var/log/messages is something we should avoid. Signed-off-by: Anand Jain <Anand.Jain@oracle.com> Reviewed-by: David Sterba <dsterba@suse.cz> Signed-off-by: Chris Mason <clm@fb.com>
This commit is contained in:
parent
67a77eb147
commit
402a0f4759
|
@ -374,11 +374,8 @@ static ssize_t btrfs_label_store(struct kobject *kobj,
|
||||||
struct btrfs_root *root = fs_info->fs_root;
|
struct btrfs_root *root = fs_info->fs_root;
|
||||||
int ret;
|
int ret;
|
||||||
|
|
||||||
if (len >= BTRFS_LABEL_SIZE) {
|
if (len >= BTRFS_LABEL_SIZE)
|
||||||
pr_err("BTRFS: unable to set label with more than %d bytes\n",
|
|
||||||
BTRFS_LABEL_SIZE - 1);
|
|
||||||
return -EINVAL;
|
return -EINVAL;
|
||||||
}
|
|
||||||
|
|
||||||
trans = btrfs_start_transaction(root, 0);
|
trans = btrfs_start_transaction(root, 0);
|
||||||
if (IS_ERR(trans))
|
if (IS_ERR(trans))
|
||||||
|
|
Loading…
Reference in a new issue