On 2019-09-24 19:34, Jason Baron wrote:
On 9/23/19 3:23 PM, Roman Penyaev wrote:
On 2019-09-23 17:43, Jason Baron wrote:
On 9/4/19 4:22 PM, Jason Baron wrote:
Currently, ep_poll_safewake() in the CONFIG_DEBUG_LOCK_ALLOC case
uses
ep_call_nested() in order to pass the correct subclass
On 9/23/19 3:23 PM, Roman Penyaev wrote:
> On 2019-09-23 17:43, Jason Baron wrote:
>> On 9/4/19 4:22 PM, Jason Baron wrote:
>>> Currently, ep_poll_safewake() in the CONFIG_DEBUG_LOCK_ALLOC case uses
>>> ep_call_nested() in order to pass the correct subclass argument to
>>>
On 2019-09-23 17:43, Jason Baron wrote:
On 9/4/19 4:22 PM, Jason Baron wrote:
Currently, ep_poll_safewake() in the CONFIG_DEBUG_LOCK_ALLOC case uses
ep_call_nested() in order to pass the correct subclass argument to
spin_lock_irqsave_nested(). However, ep_call_nested() adds unnecessary
checks
On 9/4/19 4:22 PM, Jason Baron wrote:
> Currently, ep_poll_safewake() in the CONFIG_DEBUG_LOCK_ALLOC case uses
> ep_call_nested() in order to pass the correct subclass argument to
> spin_lock_irqsave_nested(). However, ep_call_nested() adds unnecessary
> checks for epoll depth and loops that
Currently, ep_poll_safewake() in the CONFIG_DEBUG_LOCK_ALLOC case uses
ep_call_nested() in order to pass the correct subclass argument to
spin_lock_irqsave_nested(). However, ep_call_nested() adds unnecessary
checks for epoll depth and loops that are already verified when doing
EPOLL_CTL_ADD. This
5 matches
Mail list logo