From: Michael Halcrow <mhalcrow@us.ibm.com>
To: Andrea Righi <righiandr@users.sourceforge.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Rusty Russell <prussell@au1.ibm.com>,
"David J. Kleikamp" <shaggy@us.ibm.com>,
"SERGE E. HALLYN" <sergeh@us.ibm.com>
Subject: Re: [PATCH] eCryptfs: Privileged kthread for lower file opens
Date: Wed, 21 May 2008 10:14:30 -0500 [thread overview]
Message-ID: <20080521151430.GG32643@halcrowt61p.austin.ibm.com> (raw)
In-Reply-To: <48335BBF.2040901@users.sourceforge.net>
On Wed, May 21, 2008 at 01:16:15AM +0200, Andrea Righi wrote:
> Michael Halcrow wrote:
>> + req = kmem_cache_alloc(ecryptfs_open_req_cache, GFP_KERNEL);
>> + if (!req) {
>> + rc = -ENOMEM;
>> + goto out;
>> + }
>> + mutex_init(&req->mux);
>> + req->lower_file = lower_file;
>> + req->lower_dentry = lower_dentry;
>> + req->lower_mnt = lower_mnt;
>> + req->requesting_task = current;
>> + req->flags = 0;
>> + mutex_lock(&ecryptfs_kthread_ctl.mux);
>> + mutex_lock(&req->mux);
>> + if (ecryptfs_kthread_ctl.flags & ECRYPTFS_KTHREAD_ZOMBIE) {
>> + rc = -EIO;
>
> Isn't a mutex_unlock(&req->mux) missing here?
Nobody else actually has a reference to req at this point, so the
unlock is not really necessary. It might not be a bad idea to jump to
out_unlock anyway just to avoid future bugs.
>> + mutex_unlock(&ecryptfs_kthread_ctl.mux);
>> + printk(KERN_ERR "%s: We are in the middle of shutting down; "
>> + "aborting privileged request to open lower file\n",
>> + __func__);
>> + goto out_free;
>> + }
>> + list_add_tail(&req->kthread_ctl_list, &ecryptfs_kthread_ctl.req_list);
>> + mutex_unlock(&req->mux);
>> + mutex_unlock(&ecryptfs_kthread_ctl.mux);
>> + wake_up(&ecryptfs_kthread_ctl.wait);
>> +schedule:
>> + set_current_state(TASK_INTERRUPTIBLE);
>> + schedule();
>> + mutex_lock(&req->mux);
>> + if (req->flags == 0) {
>> + mutex_unlock(&req->mux);
>> + goto schedule;
>> + }
>> + set_current_state(TASK_RUNNING);
>> + if (req->flags & ECRYPTFS_REQ_DROPPED
>> + || req->flags & ECRYPTFS_REQ_ZOMBIE) {
>> + rc = -EIO;
>> + printk(KERN_WARNING "%s: Privileged open request dropped\n",
>> + __func__);
>> + goto out_unlock;
>> + }
>> + if (IS_ERR(*req->lower_file)) {
>> + rc = PTR_ERR(*req->lower_file);
>> + dget(lower_dentry);
>> + mntget(lower_mnt);
>> + (*lower_file) = dentry_open(lower_dentry, lower_mnt,
>> + (O_RDONLY | O_LARGEFILE));
>> + if (IS_ERR(*lower_file)) {
>> + rc = PTR_ERR(*req->lower_file);
>> + (*lower_file) = NULL;
>> + printk(KERN_WARNING "%s: Error attempting privileged "
>> + "open of lower file with either RW or RO "
>> + "perms; rc = [%d]. Giving up.\n",
>> + __func__, rc);
>> + }
>> + }
>> +out_unlock:
>> + mutex_unlock(&req->mux);
>> +out_free:
>> + kmem_cache_free(ecryptfs_open_req_cache, req);
>> +out:
>> + return rc;
>> +}
next prev parent reply other threads:[~2008-05-21 15:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 21:46 Michael Halcrow
2008-05-20 23:16 ` Andrea Righi
2008-05-21 15:14 ` Michael Halcrow [this message]
2008-05-21 15:39 ` [PATCH] eCryptfs: Remove useless lock Michael Halcrow
2008-05-21 22:59 ` [PATCH] eCryptfs: Privileged kthread for lower file opens Andrew Morton
2008-05-22 19:31 ` [PATCH] eCryptfs: Clean up kthread synchronization Michael Halcrow
2008-05-22 19:41 ` Andrew Morton
2008-05-22 21:16 ` Michael Halcrow
2008-05-22 21:44 ` [PATCH] eCryptfs: Use kthread_should_stop() instead of the non-empty list hack Michael Halcrow
2008-05-22 22:03 ` [PATCH] eCryptfs: Clean up kthread synchronization 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=20080521151430.GG32643@halcrowt61p.austin.ibm.com \
--to=mhalcrow@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prussell@au1.ibm.com \
--cc=righiandr@users.sourceforge.net \
--cc=sergeh@us.ibm.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 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®