From: Andrew Morton <akpm@linux-foundation.org>
To: ocfs2-devel@oss.oracle.com
Subject: Re: [PATCH 1/2] ocfs2: fix error handling in ocfs2_ioctl_move_extents()
Date: Tue, 09 Apr 2013 20:09:48 +0000 [thread overview]
Message-ID: <20130409130948.a6ea97e8fd48c69a0389390c@linux-foundation.org> (raw)
In-Reply-To: <51638854.8020405@oracle.com>
On Tue, 09 Apr 2013 11:17:40 +0800 Jeff Liu <jeff.liu@oracle.com> wrote:
> From: Dan Carpenter <dan.carpenter@oracle.com>
>
> 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>
I've added your signed-off-by to these patches - it should have been
included because you were on the patch delivery path.
prev parent reply other threads:[~2013-04-09 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 3:17 [PATCH 1/2] ocfs2: fix error handling in ocfs2_ioctl_move_extents() Jeff Liu
2013-04-09 20:09 ` Andrew Morton [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=20130409130948.a6ea97e8fd48c69a0389390c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--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