From: Tyler Hicks <tyhicks@linux.vnet.ibm.com>
To: Andy Whitcroft <apw@canonical.com>
Cc: Dustin Kirkland <kirkland@canonical.com>,
ecryptfs-devel@lists.launchpad.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] ecryptfs: read on a directory should return EISDIR if not supported
Date: Thu, 17 Feb 2011 21:48:44 -0600 [thread overview]
Message-ID: <20110218034843.GF24444@boyd.l.tihix.com> (raw)
In-Reply-To: <1297831799-5169-1-git-send-email-apw@canonical.com>
On Wed Feb 16, 2011 at 04:49:59AM +0000, Andy Whitcroft <apw@canonical.com> wrote:
> read() calls against a file descriptor connected to a directory are
> incorrectly returning EINVAL rather than EISDIR:
>
> [EISDIR]
> [XSI] [Option Start] The fildes argument refers to a directory and the
> implementation does not allow the directory to be read using read()
> or pread(). The readdir() function should be used instead. [Option End]
>
> This occurs because we do not have a .read operation defined for
> ecryptfs directories. Connect this up to generic_read_dir().
>
> BugLink: http://bugs.launchpad.net/bugs/719691
> Signed-off-by: Andy Whitcroft <apw@canonical.com>
Thanks Andy - applied to
git://git.kernel.org/pub/scm/linux/kernel/git/ecryptfs/ecryptfs-2.6.git#next
Tyler
> ---
> fs/ecryptfs/file.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/fs/ecryptfs/file.c b/fs/ecryptfs/file.c
> index 81e10e6..7d1050e 100644
> --- a/fs/ecryptfs/file.c
> +++ b/fs/ecryptfs/file.c
> @@ -317,6 +317,7 @@ ecryptfs_compat_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
>
> const struct file_operations ecryptfs_dir_fops = {
> .readdir = ecryptfs_readdir,
> + .read = generic_read_dir,
> .unlocked_ioctl = ecryptfs_unlocked_ioctl,
> #ifdef CONFIG_COMPAT
> .compat_ioctl = ecryptfs_compat_ioctl,
> --
> 1.7.1
>
prev parent reply other threads:[~2011-02-18 3:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 4:49 Andy Whitcroft
2011-02-18 3:48 ` Tyler Hicks [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=20110218034843.GF24444@boyd.l.tihix.com \
--to=tyhicks@linux.vnet.ibm.com \
--cc=apw@canonical.com \
--cc=ecryptfs-devel@lists.launchpad.net \
--cc=kirkland@canonical.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®