From: Filipe David Borba Manana <fdmanana@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: Filipe David Borba Manana <fdmanana@gmail.com>
Subject: [PATCH 0/2] BTRFS_IOC_INO_LOOKUP ioctl fixes
Date: Wed, 14 Aug 2013 03:00:19 +0100 [thread overview]
Message-ID: <1376445621-18561-1-git-send-email-fdmanana@gmail.com> (raw)
This set of patches fixes 2 issues with the BTRFS_IOC_INO_LOOKUP ioctl:
1) missing error code return when path is too long;
2) ocassional ENOENT error even when the desired inode ref items exist.
Filipe David Borba Manana (2):
Btrfs: add missing error code to BTRFS_IOC_INO_LOOKUP handler
Btrfs: don't miss inode ref items in BTRFS_IOC_INO_LOOKUP
fs/btrfs/ioctl.c | 24 +++++++++++++-----------
1 file changed, 13 insertions(+), 11 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-08-14 2:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 2:00 Filipe David Borba Manana [this message]
2013-08-14 2:00 ` [PATCH 1/2] Btrfs: add missing error code to BTRFS_IOC_INO_LOOKUP handler Filipe David Borba Manana
2013-08-14 2:00 ` [PATCH 2/2] Btrfs: don't miss inode ref items in BTRFS_IOC_INO_LOOKUP Filipe David Borba Manana
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=1376445621-18561-1-git-send-email-fdmanana@gmail.com \
--to=fdmanana@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).