Re: nfs: possible sync issue between nfs_call_unlink <-> nfs_async_unlink_release

2018-11-13 Thread Rafael David Tinoco
On 7/3/18 6:04 PM, Rafael Tinoco wrote: BUG: https://bugs.linaro.org/show_bug.cgi?id=3731 During Linaro's Kernel Functional tests, we have observed the following situation: [ 52.651490] DEBUG_LOCKS_WARN_ON(sem->owner != ((struct task_struct *)1UL)) [ 52.651506] WARNING: CPU: 2 PID: 1457 at

Re: nfs: possible sync issue between nfs_call_unlink <-> nfs_async_unlink_release

2018-11-13 Thread Rafael David Tinoco
On 7/3/18 6:04 PM, Rafael Tinoco wrote: BUG: https://bugs.linaro.org/show_bug.cgi?id=3731 During Linaro's Kernel Functional tests, we have observed the following situation: [ 52.651490] DEBUG_LOCKS_WARN_ON(sem->owner != ((struct task_struct *)1UL)) [ 52.651506] WARNING: CPU: 2 PID: 1457 at

nfs: possible sync issue between nfs_call_unlink <-> nfs_async_unlink_release

2018-07-03 Thread Rafael Tinoco
BUG: https://bugs.linaro.org/show_bug.cgi?id=3731 During Linaro's Kernel Functional tests, we have observed the following situation: [ 52.651490] DEBUG_LOCKS_WARN_ON(sem->owner != ((struct task_struct *)1UL)) [ 52.651506] WARNING: CPU: 2 PID: 1457 at ./kernel/locking/rwsem.c:217

nfs: possible sync issue between nfs_call_unlink <-> nfs_async_unlink_release

2018-07-03 Thread Rafael Tinoco
BUG: https://bugs.linaro.org/show_bug.cgi?id=3731 During Linaro's Kernel Functional tests, we have observed the following situation: [ 52.651490] DEBUG_LOCKS_WARN_ON(sem->owner != ((struct task_struct *)1UL)) [ 52.651506] WARNING: CPU: 2 PID: 1457 at ./kernel/locking/rwsem.c:217