public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Liu <jeff.liu@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: Re: [patch 1/2 v2] Ocfs2/move_extents: fix error handling in ioctl
Date: Thu, 04 Apr 2013 11:52:36 +0000	[thread overview]
Message-ID: <515D6984.9030204@oracle.com> (raw)
In-Reply-To: <20130404114030.GA25020@longonot.mountain>

On 04/04/2013 07:40 PM, Dan Carpenter wrote:
> Smatch complains that if we hit an error (for example if the file is
> immutable) then "range" has uninitialized stack data and we copy it to
> the user.
> 
> I've re-written the error handling to avoid this problem and make it a
> little cleaner as well.
> 
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Reviewed-by: Jie Liu <jeff.liu@oracle.com>

> ---
> v2: check for argp earlier
> 
> diff --git a/fs/ocfs2/move_extents.c b/fs/ocfs2/move_extents.c
> index 9f8dcad..8f3d3cb 100644
> --- a/fs/ocfs2/move_extents.c
> +++ b/fs/ocfs2/move_extents.c
> @@ -1057,42 +1057,40 @@ int ocfs2_ioctl_move_extents(struct file *filp, void __user *argp)
>  
>  	struct inode *inode = file_inode(filp);
>  	struct ocfs2_move_extents range;
> -	struct ocfs2_move_extents_context *context = NULL;
> +	struct ocfs2_move_extents_context *context;
> +
> +	if (!argp)
> +		return -EINVAL;
>  
>  	status = mnt_want_write_file(filp);
>  	if (status)
>  		return status;
>  
>  	if ((!S_ISREG(inode->i_mode)) || !(filp->f_mode & FMODE_WRITE))
> -		goto out;
> +		goto out_drop;
>  
>  	if (inode->i_flags & (S_IMMUTABLE|S_APPEND)) {
>  		status = -EPERM;
> -		goto out;
> +		goto out_drop;
>  	}
>  
>  	context = kzalloc(sizeof(struct ocfs2_move_extents_context), GFP_NOFS);
>  	if (!context) {
>  		status = -ENOMEM;
>  		mlog_errno(status);
> -		goto out;
> +		goto out_drop;
>  	}
>  
>  	context->inode = inode;
>  	context->file = filp;
>  
> -	if (argp) {
> -		if (copy_from_user(&range, argp, sizeof(range))) {
> -			status = -EFAULT;
> -			goto out;
> -		}
> -	} else {
> -		status = -EINVAL;
> -		goto out;
> +	if (copy_from_user(&range, argp, sizeof(range))) {
> +		status = -EFAULT;
> +		goto out_free;
>  	}
>  
>  	if (range.me_start > i_size_read(inode))
> -		goto out;
> +		goto out_free;
>  
>  	if (range.me_start + range.me_len > i_size_read(inode))
>  			range.me_len = i_size_read(inode) - range.me_start;
> @@ -1124,25 +1122,24 @@ int ocfs2_ioctl_move_extents(struct file *filp, void __user *argp)
>  
>  		status = ocfs2_validate_and_adjust_move_goal(inode, &range);
>  		if (status)
> -			goto out;
> +			goto out_copy;
>  	}
>  
>  	status = ocfs2_move_extents(context);
>  	if (status)
>  		mlog_errno(status);
> -out:
> +out_copy:
>  	/*
>  	 * movement/defragmentation may end up being partially completed,
>  	 * that's the reason why we need to return userspace the finished
>  	 * length and new_offset even if failure happens somewhere.
>  	 */
> -	if (argp) {
> -		if (copy_to_user(argp, &range, sizeof(range)))
> -			status = -EFAULT;
> -	}
> +	if (copy_to_user(argp, &range, sizeof(range)))
> +		status = -EFAULT;
>  
> +out_free:
>  	kfree(context);
> -
> +out_drop:
>  	mnt_drop_write_file(filp);
>  
>  	return status;
> --
> To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


  reply	other threads:[~2013-04-04 11:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04  6:37 [patch 1/2] Ocfs2/move_extents: fix error handling in ioctl Dan Carpenter
2013-04-04  9:21 ` Jeff Liu
2013-04-04 11:40   ` [patch 1/2 v2] " Dan Carpenter
2013-04-04 11:52     ` Jeff Liu [this message]
2013-04-09  0:04       ` [Ocfs2-devel] " Andrew Morton
2013-04-09  3:13         ` Jeff Liu

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=515D6984.9030204@oracle.com \
    --to=jeff.liu@oracle.com \
    --cc=ocfs2-devel@oss.oracle.com \
    /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