Re: [PATCH] zram: move comp allocation out of init_lock

2014-03-06 Thread Sergey Senozhatsky
Hello Minchan, On (03/06/14 17:26), Minchan Kim wrote: > Hello Sergey, > > On Tue, Mar 04, 2014 at 01:10:56PM +0300, Sergey Senozhatsky wrote: > > While fixing lockdep spew of ->init_lock reported by Sasha Levin [1], > > Minchan > > Kim noted [2] that it's better to move compression backend

Re: [PATCH] zram: move comp allocation out of init_lock

2014-03-06 Thread Minchan Kim
Hello Sergey, On Tue, Mar 04, 2014 at 01:10:56PM +0300, Sergey Senozhatsky wrote: > While fixing lockdep spew of ->init_lock reported by Sasha Levin [1], Minchan > Kim noted [2] that it's better to move compression backend allocation (using > GPF_KERNEL) out of the ->init_lock lock, same way as

Re: [PATCH] zram: move comp allocation out of init_lock

2014-03-06 Thread Minchan Kim
Hello Sergey, On Tue, Mar 04, 2014 at 01:10:56PM +0300, Sergey Senozhatsky wrote: While fixing lockdep spew of -init_lock reported by Sasha Levin [1], Minchan Kim noted [2] that it's better to move compression backend allocation (using GPF_KERNEL) out of the -init_lock lock, same way as with

Re: [PATCH] zram: move comp allocation out of init_lock

2014-03-06 Thread Sergey Senozhatsky
Hello Minchan, On (03/06/14 17:26), Minchan Kim wrote: Hello Sergey, On Tue, Mar 04, 2014 at 01:10:56PM +0300, Sergey Senozhatsky wrote: While fixing lockdep spew of -init_lock reported by Sasha Levin [1], Minchan Kim noted [2] that it's better to move compression backend allocation

Re: [PATCH] zram: move comp allocation out of init_lock

2014-03-05 Thread Sergey Senozhatsky
On (03/05/14 15:57), Jerome Marchand wrote: > On 03/04/2014 11:10 AM, Sergey Senozhatsky wrote: > > While fixing lockdep spew of ->init_lock reported by Sasha Levin [1], > > Minchan > > Kim noted [2] that it's better to move compression backend allocation (using > > GPF_KERNEL) out of the

Re: [PATCH] zram: move comp allocation out of init_lock

2014-03-05 Thread Jerome Marchand
On 03/04/2014 11:10 AM, Sergey Senozhatsky wrote: > While fixing lockdep spew of ->init_lock reported by Sasha Levin [1], Minchan > Kim noted [2] that it's better to move compression backend allocation (using > GPF_KERNEL) out of the ->init_lock lock, same way as with zram_meta_alloc(), > in order

Re: [PATCH] zram: move comp allocation out of init_lock

2014-03-05 Thread Jerome Marchand
On 03/04/2014 11:10 AM, Sergey Senozhatsky wrote: While fixing lockdep spew of -init_lock reported by Sasha Levin [1], Minchan Kim noted [2] that it's better to move compression backend allocation (using GPF_KERNEL) out of the -init_lock lock, same way as with zram_meta_alloc(), in order to

Re: [PATCH] zram: move comp allocation out of init_lock

2014-03-05 Thread Sergey Senozhatsky
On (03/05/14 15:57), Jerome Marchand wrote: On 03/04/2014 11:10 AM, Sergey Senozhatsky wrote: While fixing lockdep spew of -init_lock reported by Sasha Levin [1], Minchan Kim noted [2] that it's better to move compression backend allocation (using GPF_KERNEL) out of the -init_lock lock,

[PATCH] zram: move comp allocation out of init_lock

2014-03-04 Thread Sergey Senozhatsky
While fixing lockdep spew of ->init_lock reported by Sasha Levin [1], Minchan Kim noted [2] that it's better to move compression backend allocation (using GPF_KERNEL) out of the ->init_lock lock, same way as with zram_meta_alloc(), in order to prevent the same lockdep spew. [1]

[PATCH] zram: move comp allocation out of init_lock

2014-03-04 Thread Sergey Senozhatsky
While fixing lockdep spew of -init_lock reported by Sasha Levin [1], Minchan Kim noted [2] that it's better to move compression backend allocation (using GPF_KERNEL) out of the -init_lock lock, same way as with zram_meta_alloc(), in order to prevent the same lockdep spew. [1]