From: Andrew Morton <akpm@linux-foundation.org>
To: ocfs2-devel@oss.oracle.com
Subject: Re: [Ocfs2-devel] [patch 1/2 v2] Ocfs2/move_extents: fix error handling in ioctl
Date: Tue, 09 Apr 2013 00:04:09 +0000 [thread overview]
Message-ID: <20130408170409.b16252fc16e9cdc8abfc91eb@linux-foundation.org> (raw)
In-Reply-To: <515D6984.9030204@oracle.com>
On Thu, 04 Apr 2013 19:52:36 +0800 Jeff Liu <jeff.liu@oracle.com> wrote:
> 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>
I can't find either of Dan's emails anywhere. Confused.
Resend both, please?
next prev parent reply other threads:[~2013-04-09 0:04 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
2013-04-09 0:04 ` Andrew Morton [this message]
2013-04-09 3:13 ` [Ocfs2-devel] " 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=20130408170409.b16252fc16e9cdc8abfc91eb@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