From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Li Bin <huawei.libin@huawei.com>
Cc: sjenning@redhat.com, jikos@kernel.org, vojtech@suse.com,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
guohanjun@huawei.com, dingtianhong@huawei.com,
xiexiuqi@huawei.com, zhouchengming1@huawei.com,
Miroslav Benes <mbenes@suse.cz>
Subject: Re: [PATCH] livepatch: fix race between enabled_store() and klp_unregister_patch()
Date: Mon, 30 Nov 2015 19:11:39 -0600 [thread overview]
Message-ID: <20151201011139.GB12513@treble.redhat.com> (raw)
In-Reply-To: <1448855677-8392-1-git-send-email-huawei.libin@huawei.com>
On Mon, Nov 30, 2015 at 11:54:37AM +0800, Li Bin wrote:
> There is a potential race as following:
>
> CPU0 | CPU1
> -----------------------------|-----------------------------------
> enabled_store() | klp_unregister_patch()
> | |-mutex_lock(&klp_mutex);
> |-mutex_lock(&klp_mutex); | |-klp_free_patch();
> | |-mutex_unlock(&klp_mutex);
> |-[process the patch's state]|
> |-mutex_unlock(&klp_mutex) |
>
> Fix this race condition by adding klp_is_patch_registered() check in
> enabled_store() after get the lock klp_mutex.
I'm thinking this race isn't possible, and that instead it would
deadlock.
When I try to recreate something similar by putting a delay in
enabled_store(), klp_free_patch() just sleeps on its call to
kobject_put() until enabled_store() returns. The unregister stack looks
like:
[<ffffffff812e966b>] __kernfs_remove+0x1fb/0x380
[<ffffffff812ea273>] kernfs_remove+0x23/0x40
[<ffffffff812ec601>] sysfs_remove_dir+0x51/0x80
[<ffffffff81407fb8>] kobject_del+0x18/0x50
[<ffffffff8140804a>] kobject_release+0x5a/0x190
[<ffffffff81407f27>] kobject_put+0x27/0x50
[<ffffffff81128d41>] klp_unregister_patch+0x71/0x80
It seems to be waiting on a lock which is held by the kernfs code which
called enabled_store(). So when enabled_store() tries to get the
klp_mutex, it deadlocks.
Miroslav and I previously discussed a few options to fix this:
https://lkml.kernel.org/r/alpine.LNX.2.00.1502171728520.29490@pobox.suse.cz
--
Josh
next prev parent reply other threads:[~2015-12-01 1:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 3:54 Li Bin
2015-11-30 13:53 ` Petr Mladek
2015-12-01 1:11 ` Josh Poimboeuf [this message]
2015-12-01 2:46 ` libin
2015-12-01 8:50 ` Jiri Slaby
2015-12-01 14:13 ` Petr Mladek
2015-12-01 14:28 ` Jiri Slaby
2015-12-01 16:57 ` Petr Mladek
2015-12-01 15:53 ` Josh Poimboeuf
2015-12-15 8:14 ` Miroslav Benes
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=20151201011139.GB12513@treble.redhat.com \
--to=jpoimboe@redhat.com \
--cc=dingtianhong@huawei.com \
--cc=guohanjun@huawei.com \
--cc=huawei.libin@huawei.com \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=sjenning@redhat.com \
--cc=vojtech@suse.com \
--cc=xiexiuqi@huawei.com \
--cc=zhouchengming1@huawei.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®