Re: [f2fs-dev] [PATCH] f2fs: do not use mutex lock in atomic context

2019-02-17 Thread Ritesh Harjani
On 2/15/2019 2:40 PM, Chao Yu wrote: On 2019/2/15 12:28, Ritesh Harjani wrote: On 2/14/2019 9:40 PM, Chao Yu wrote: On 2019-2-14 15:46, Sahitya Tummala wrote: On Wed, Feb 13, 2019 at 11:25:31AM +0800, Chao Yu wrote: On 2019/2/4 16:06, Sahitya Tummala wrote: Fix below warning coming because

Re: [f2fs-dev] [PATCH] f2fs: do not use mutex lock in atomic context

2019-02-15 Thread Chao Yu
On 2019/2/15 12:28, Ritesh Harjani wrote: > > On 2/14/2019 9:40 PM, Chao Yu wrote: >> On 2019-2-14 15:46, Sahitya Tummala wrote: >>> On Wed, Feb 13, 2019 at 11:25:31AM +0800, Chao Yu wrote: On 2019/2/4 16:06, Sahitya Tummala wrote: > Fix below warning coming because of using mutex lock in

Re: [f2fs-dev] [PATCH] f2fs: do not use mutex lock in atomic context

2019-02-14 Thread Ritesh Harjani
On 2/14/2019 9:40 PM, Chao Yu wrote: On 2019-2-14 15:46, Sahitya Tummala wrote: On Wed, Feb 13, 2019 at 11:25:31AM +0800, Chao Yu wrote: On 2019/2/4 16:06, Sahitya Tummala wrote: Fix below warning coming because of using mutex lock in atomic context. BUG: sleeping function called from inval

Re: [f2fs-dev] [PATCH] f2fs: do not use mutex lock in atomic context

2019-02-14 Thread Chao Yu
On 2019-2-14 15:46, Sahitya Tummala wrote: > On Wed, Feb 13, 2019 at 11:25:31AM +0800, Chao Yu wrote: >> On 2019/2/4 16:06, Sahitya Tummala wrote: >>> Fix below warning coming because of using mutex lock in atomic context. >>> >>> BUG: sleeping function called from invalid context at >>> kernel/lo

Re: [PATCH] f2fs: do not use mutex lock in atomic context

2019-02-13 Thread Sahitya Tummala
On Wed, Feb 13, 2019 at 11:25:31AM +0800, Chao Yu wrote: > On 2019/2/4 16:06, Sahitya Tummala wrote: > > Fix below warning coming because of using mutex lock in atomic context. > > > > BUG: sleeping function called from invalid context at > > kernel/locking/mutex.c:98 > > in_atomic(): 1, irqs_dis

Re: [PATCH] f2fs: do not use mutex lock in atomic context

2019-02-12 Thread Chao Yu
On 2019/2/4 16:06, Sahitya Tummala wrote: > Fix below warning coming because of using mutex lock in atomic context. > > BUG: sleeping function called from invalid context at > kernel/locking/mutex.c:98 > in_atomic(): 1, irqs_disabled(): 0, pid: 585, name: sh > Preemption disabled at: __radix_tree

[PATCH] f2fs: do not use mutex lock in atomic context

2019-02-04 Thread Sahitya Tummala
Fix below warning coming because of using mutex lock in atomic context. BUG: sleeping function called from invalid context at kernel/locking/mutex.c:98 in_atomic(): 1, irqs_disabled(): 0, pid: 585, name: sh Preemption disabled at: __radix_tree_preload+0x28/0x130 Call trace: dump_backtrace+0x0/0x2