From: Rik van Riel <riel@redhat.com>
To: Oleg Nesterov <oleg@redhat.com>
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
Date: Wed, 13 Aug 2014 12:09:16 -0400 [thread overview]
Message-ID: <53EB8DAC.1040605@redhat.com> (raw)
In-Reply-To: <20140813155802.GA2695@redhat.com>
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...
next prev parent reply other threads:[~2014-08-13 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 15:50 [PATCH] fix sighand use after free Rik van Riel
2014-08-13 15:58 ` Oleg Nesterov
2014-08-13 16:09 ` Rik van Riel [this message]
2014-08-13 16:19 ` Oleg Nesterov
2014-08-13 16:43 ` Rik van Riel
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=53EB8DAC.1040605@redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.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 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.