From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: [PATCH -rt] rt-slab: fix cpu inconsistency case
Date: Mon, 24 Mar 2008 14:11:00 -0700 [thread overview]
Message-ID: <47E818E4.2050602@ct.jp.nec.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0803241639220.9884@gandalf.stny.rr.com>
Steven Rostedt wrote:
> On Mon, 24 Mar 2008, Steven Rostedt wrote:
>
>> On Fri, 21 Mar 2008, Hiroshi Shimamoto wrote:
>>>> Is this a bug in mainline? The !PREEMPT_RT case should be as close to
>>>> mainline as possible, with no actual changes in object code. If this is
>>>> not the case, then we need to fix that.
>>> No, this issue is in -rt only.
>>>
>> Hi Hiroshi,
>>
>> Thanks again for reporting this. I took a deeper look into this today and
>> came to the conclusion that we need to get rid of both
>> slab_irq_disable_nort and slab_irq_disable_rt, and simply use
>> slab_irq_disable ;-)
>>
>> This is what you patch indirectly does. I'll write up another patch to fix
>> this.
>>
>
> Actually, I'm going to take your patch.
>
> Seems that the reason Ingo did the two separate, is that the functions
> called also call the slab_irq_save, which will retake the locks in
> PREEMPT_RT. If we don't release the lock, then we can deadlock.
>
OK, actually, I had a interest in your rework :-)
thanks,
Hiroshi Shimamoto
next prev parent reply other threads:[~2008-03-24 21:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 18:00 [PATCH -rt] rt-slab: fix cpu inconsistency case Hiroshi Shimamoto
2008-03-20 19:32 ` Steven Rostedt
2008-03-20 20:10 ` Hiroshi Shimamoto
2008-03-21 20:37 ` Steven Rostedt
2008-03-21 20:47 ` Hiroshi Shimamoto
2008-03-24 20:35 ` Steven Rostedt
2008-03-24 20:40 ` Steven Rostedt
2008-03-24 21:11 ` Hiroshi Shimamoto [this message]
2008-03-24 20:54 ` Hiroshi Shimamoto
2008-03-21 18:11 ` Daniel Walker
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=47E818E4.2050602@ct.jp.nec.com \
--to=h-shimamoto@ct.jp.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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