On Mon, 28 Mar 2016, Dave Jones wrote:
> I hit this a few days ago. I'm not 100% what kernel it was running,
> but I'm pretty sure it was a post 4.5 kernel from this merge window.
Thanks for the report. All consistent with shmem_fallocate() somehow
getting through its wake_up_all() without
On Mon, 28 Mar 2016, Dave Jones wrote:
> I hit this a few days ago. I'm not 100% what kernel it was running,
> but I'm pretty sure it was a post 4.5 kernel from this merge window.
Thanks for the report. All consistent with shmem_fallocate() somehow
getting through its wake_up_all() without
I hit this a few days ago. I'm not 100% what kernel it was running,
but I'm pretty sure it was a post 4.5 kernel from this merge window.
WARNING: CPU: 2 PID: 28919 at kernel/locking/lockdep.c:3198
__lock_acquire+0x74d/0x1c60
DEBUG_LOCKS_WARN_ON(class_idx > MAX_LOCKDEP_KEYS)
CPU: 2 PID: 28919
I hit this a few days ago. I'm not 100% what kernel it was running,
but I'm pretty sure it was a post 4.5 kernel from this merge window.
WARNING: CPU: 2 PID: 28919 at kernel/locking/lockdep.c:3198
__lock_acquire+0x74d/0x1c60
DEBUG_LOCKS_WARN_ON(class_idx > MAX_LOCKDEP_KEYS)
CPU: 2 PID: 28919
4 matches
Mail list logo