From: David Sterba <dsterba@suse.cz>
To: Chengyu Song <csong84@gatech.edu>
Cc: clm@fb.com, jbacik@fb.com, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org, taesoo@gatech.edu,
changwoo@gatech.edu, sanidhya@gatech.edu, blee@gatech.edu
Subject: Re: [PATCH 1/1] btrfs: incorrect handling for fiemap_fill_next_extent return
Date: Tue, 24 Mar 2015 23:25:54 +0100 [thread overview]
Message-ID: <20150324222554.GZ20767@suse.cz> (raw)
In-Reply-To: <1427235176-19381-1-git-send-email-csong84@gatech.edu>
On Tue, Mar 24, 2015 at 06:12:56PM -0400, Chengyu Song wrote:
> fiemap_fill_next_extent returns 0 on success, -errno on error, 1 if this was
> the last extent that will fit in user array. If 1 is returned, the return
> value may eventually returned to user space, which should not happen, according
> to manpage of ioctl.
>
> Signed-off-by: Chengyu Song <csong84@gatech.edu>
Good catch, thanks.
Reviewed-by: David Sterba <dsterba@suse.cz>
Should go to stable.
prev parent reply other threads:[~2015-03-24 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 22:12 Chengyu Song
2015-03-24 22:25 ` David Sterba [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=20150324222554.GZ20767@suse.cz \
--to=dsterba@suse.cz \
--cc=blee@gatech.edu \
--cc=changwoo@gatech.edu \
--cc=clm@fb.com \
--cc=csong84@gatech.edu \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sanidhya@gatech.edu \
--cc=taesoo@gatech.edu \
/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
all inboxes | Powered by JetHome®