From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753288AbaHMQKw (ORCPT ); Wed, 13 Aug 2014 12:10:52 -0400 Received: from mx1.redhat.com ([209.132.183.28]:63102 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751145AbaHMQKv (ORCPT ); Wed, 13 Aug 2014 12:10:51 -0400 Message-ID: <53EB8DAC.1040605@redhat.com> Date: Wed, 13 Aug 2014 12:09:16 -0400 From: Rik van Riel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Oleg Nesterov CC: linux-kernel@vger.kernel.org, akpm@linux-foundation.org, peterz@infradead.org, paulmck@linux.vnet.ibm.com Subject: Re: [PATCH] fix sighand use after free References: <20140813115000.73da6136@cuia.bos.redhat.com> <20140813155802.GA2695@redhat.com> In-Reply-To: <20140813155802.GA2695@redhat.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/13/2014 11:58 AM, Oleg Nesterov wrote: > On 08/13, Rik van Riel wrote: >> >> Subject: fix sighand use after free >> >> __lock_task_sighand carefully takes the rcu_read_lock, gets >> tsk->sighand with rcu_dereference, and verifies that the task >> is still using the sighand_struct after taking the spinlock. >> >> This works much better if the sighand struct is actually rcu >> freed. > > I promise, I'll send the doc patch soon ;) > >> --- a/kernel/fork.c >> +++ b/kernel/fork.c >> @@ -1017,7 +1017,7 @@ void __cleanup_sighand(struct sighand_struct *sighand) >> { >> if (atomic_dec_and_test(&sighand->count)) { >> signalfd_cleanup(sighand); >> - kmem_cache_free(sighand_cachep, sighand); >> + rcu_free(sighand_cachep, sighand); > > Please note that sighand_cachep is SLAB_DESTROY_BY_RCU. SLAB_DESTROY_BY_RCU means that the slab page is not given back to the system until after the RCU grace period has expired. However, the objects inside the slab can still be reused immediately! In the case of the sighand struct, we have this possible race: thread A thread B thread C gets task A->sighand kmem_cache_free sighand re-alloc sighand spin_lock sighand spin_lock_init sighand spin_unlock sighand Now task C has a sighand which can never be locked. > Hmm. and what is rcu_free() ? Ugh, that should have been kfree_rcu of course, with appropriate rcu space in the struct. Now I wonder why my test compile succeeded...