[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <02171384-9d1e-19fa-5fa1-5f84b720a03e@virtuozzo.com>
Date: Wed, 22 Dec 2021 18:50:58 +0300
From: Vasily Averin <vvs@...tuozzo.com>
To: Manfred Spraul <manfred@...orfullife.com>, cgel.zte@...il.com,
akpm@...ux-foundation.org
Cc: shakeelb@...gle.com, rdunlap@...radead.org, dbueso@...e.de,
unixbhaskar@...il.com, chi.minghao@....com.cn, arnd@...db.de,
linux-kernel@...r.kernel.org, Zeal Robot <zealci@....com.cn>
Subject: Re: [PATCH] ipc/sem: do not sleep with a spin lock held
On 22.12.2021 18:31, Vasily Averin wrote:
> On 22.12.2021 14:45, Manfred Spraul wrote:
>> Hi Minghao,
>>
>> On 12/22/21 09:10, cgel.zte@...il.com wrote:
>>> From: Minghao Chi <chi.minghao@....com.cn>
>>>
>>> We can't call kvfree() with a spin lock held, so defer it.
>
> I'm sorry, but I do not understand why exactly we cannot use kvfree?
> Could you explain it in more details?
Got it,
there is cond_resched() called in __vfree() -> __vunmap()
However I'm still not sure that in_interrupt() is used correctly here.
Thank you,
Vasily Averin
Powered by blists - more mailing lists