From: Andrew Morton <akpm@linux-foundation.org>
To: Michael Halcrow <mhalcrow@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, shaggy@us.ibm.com,
sandeen@redhat.com, jmoyer@redhat.com
Subject: Re: [PATCH] eCryptfs: Fix dentry handling on create error, unlink, and inode destroy
Date: Mon, 7 Jan 2008 21:45:17 -0800 [thread overview]
Message-ID: <20080107214517.ebf5a5bd.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080108052542.GX10989@localhost.austin.ibm.com>
On Mon, 7 Jan 2008 23:25:42 -0600 Michael Halcrow <mhalcrow@us.ibm.com> wrote:
> --- a/fs/ecryptfs/inode.c
> +++ b/fs/ecryptfs/inode.c
> @@ -120,22 +120,9 @@ ecryptfs_do_create(struct inode *directory_inode,
> rc = ecryptfs_create_underlying_file(lower_dir_dentry->d_inode,
> ecryptfs_dentry, mode, nd);
> if (rc) {
> - struct inode *ecryptfs_inode = ecryptfs_dentry->d_inode;
> - struct ecryptfs_inode_info *inode_info =
> - ecryptfs_inode_to_private(ecryptfs_inode);
> -
> - printk(KERN_WARNING "%s: Error creating underlying file; "
> - "rc = [%d]; checking for existing\n", __FUNCTION__, rc);
> - if (inode_info) {
> - mutex_lock(&inode_info->lower_file_mutex);
> - if (!inode_info->lower_file) {
> - mutex_unlock(&inode_info->lower_file_mutex);
> - printk(KERN_ERR "%s: Failure to set underlying "
> - "file; rc = [%d]\n", __FUNCTION__, rc);
> - goto out_lock;
> - }
> - mutex_unlock(&inode_info->lower_file_mutex);
> - }
> + printk(KERN_ERR "%s: Failure to create dentry in lower fs; "
> + "rc = [%d]\n", __FUNCTION__, rc);
> + goto out_lock;
> }
> rc = ecryptfs_interpose(lower_dentry, ecryptfs_dentry,
> directory_inode->i_sb, 0);
Will this cause an undesirable log storm if the underlying fs runs out of
space?
next prev parent reply other threads:[~2008-01-08 5:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 5:25 [PATCH] eCryptfs: Fix dentry handling on create error, unlink, and inode destroy Michael Halcrow
2008-01-08 5:45 ` Andrew Morton [this message]
2008-01-08 21:58 ` Michael Halcrow
2008-01-08 22:42 ` Andrew Morton
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=20080107214517.ebf5a5bd.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhalcrow@us.ibm.com \
--cc=sandeen@redhat.com \
--cc=shaggy@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.