Re: 4.5 shmem lockdep/out-of-bound/list corruption disaster

2016-03-28 Thread Hugh Dickins
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

Re: 4.5 shmem lockdep/out-of-bound/list corruption disaster

2016-03-28 Thread Hugh Dickins
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

4.5 shmem lockdep/out-of-bound/list corruption disaster

2016-03-28 Thread Dave Jones
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.5 shmem lockdep/out-of-bound/list corruption disaster

2016-03-28 Thread Dave Jones
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