From: taoyue <yue.tao@windriver.com>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Alexey Dobriyan <adobriyan@sw.ru>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Roland McGrath <roland@redhat.com>,
linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH] sigqueue_free: fix the race with collect_signal()
Date: Fri, 24 Aug 2007 17:29:47 -0400 [thread overview]
Message-ID: <46CF4DCB.6030304@windriver.com> (raw)
In-Reply-To: <20070824074558.GA86@tv-sign.ru>
Oleg Nesterov wrote:
> On 08/24, taoyue wrote:
>
>> Oleg Nesterov wrote:
>>
>>> --- t/kernel/signal.c~SQFREE 2007-08-22 20:06:31.000000000 +0400
>>> +++ t/kernel/signal.c 2007-08-23 16:02:57.000000000 +0400
>>> @@ -1297,20 +1297,19 @@ struct sigqueue *sigqueue_alloc(void)
>>> void sigqueue_free(struct sigqueue *q)
>>> {
>>> unsigned long flags;
>>> + spinlock_t *lock = ¤t->sighand->siglock;
>>> +
>>> BUG_ON(!(q->flags & SIGQUEUE_PREALLOC));
>>> /*
>>> * If the signal is still pending remove it from the
>>> - * pending queue.
>>> + * pending queue. We must hold ->siglock while testing
>>> + * q->list to serialize with collect_signal().
>>> */
>>> - if (unlikely(!list_empty(&q->list))) {
>>> - spinlock_t *lock = ¤t->sighand->siglock;
>>> - read_lock(&tasklist_lock);
>>> - spin_lock_irqsave(lock, flags);
>>> - if (!list_empty(&q->list))
>>> - list_del_init(&q->list);
>>> - spin_unlock_irqrestore(lock, flags);
>>> - read_unlock(&tasklist_lock);
>>> - }
>>> + spin_lock_irqsave(lock, flags);
>>> + if (!list_empty(&q->list))
>>> + list_del_init(&q->list);
>>> + spin_unlock_irqrestore(lock, flags);
>>> +
>>> q->flags &= ~SIGQUEUE_PREALLOC;
>>> __sigqueue_free(q);
>>> }
>>>
>>>
>>>
>>>
>> Applying previous patch???it seems likely that the __sigqueue_free() is
>> also called twice.
>>
>> collect_signal: sigqueue_free:
>>
>> list_del_init(&first->list);
>> spin_lock_irqsave(lock, flags);
>>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>> if (!list_empty(&q->list))
>> list_del_init(&q->list);
>> spin_unlock_irqrestore(lock, flags);
>> q->flags &= ~SIGQUEUE_PREALLOC;
>>
>> __sigqueue_free(first); __sigqueue_free(q);
>>
>
> collect_signal() is always called under ->siglock which is also taken by
> sigqueue_free(), so this is not possible.
>
> Basically, this patch is the same one-liner I sent you before
>
> http://marc.info/?l=linux-kernel&m=118772206603453&w=2
>
> (Thanks for the additional testing and report, btw).
>
> P.S. It would be nice to know if this patch solves the problems reported
> by Jeremy, but his email is disabled.
>
> Oleg.
>
>
I know, using current->sighand->siglock to prevent one sigqueue
is free twice. I want to know whether it is possible that the two
function is called in different thread. If that, the spin_lock is useless.
yue.tao
next prev parent reply other threads:[~2007-08-24 9:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 13:45 [PATCH] sigqueue_free: fix the race with collect_signal() Oleg Nesterov
2007-08-23 21:36 ` Sukadev Bhattiprolu
2007-08-23 22:05 ` Oleg Nesterov
2007-08-24 14:26 ` taoyue
2007-08-24 7:45 ` Oleg Nesterov
2007-08-24 21:29 ` taoyue [this message]
2007-08-24 11:08 ` Oleg Nesterov
2007-08-24 20:03 ` Sukadev Bhattiprolu
2007-08-24 20:23 ` Oleg Nesterov
2007-08-25 17:24 ` Sukadev Bhattiprolu
2007-08-25 17:34 ` Oleg Nesterov
2007-08-27 13:45 ` taoyue
2007-08-27 5:57 ` Oleg Nesterov
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=46CF4DCB.6030304@windriver.com \
--to=yue.tao@windriver.com \
--cc=adobriyan@sw.ru \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
--cc=roland@redhat.com \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
/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