Re: lockdep: holding locks across syscall boundaries

[Jens Axboe]

On 10/27/23 10:12 AM, Peter Zijlstra wrote:
> The difference is that in this case the full lock order is determined by
> kernel code (under our full control), while in the earlier example, the
> lock order is determined by syscall order -- out of our control.

Ah yes, good point - this seems like the key concept here. I think we're
better off doing this seperately and just return -EDEADLK or something
like that if it's being violated, rather than spew complaints.

Thanks!

-- 
Jens Axboe