Re: [PATCH 3/3] zram: get rid of lockdep warning

2013-01-21 Thread Minchan Kim
On Mon, Jan 21, 2013 at 02:31:47PM -0800, Nitin Gupta wrote: > On 01/20/2013 09:18 PM, Minchan Kim wrote: > >On Fri, Jan 18, 2013 at 01:34:18PM -0800, Nitin Gupta wrote: > >>On Wed, Jan 16, 2013 at 6:12 PM, Minchan Kim wrote: > >>>Lockdep complains about recursive deadlock of zram->init_lock. > >>

Re: [PATCH 3/3] zram: get rid of lockdep warning

2013-01-21 Thread Nitin Gupta
On 01/20/2013 09:18 PM, Minchan Kim wrote: On Fri, Jan 18, 2013 at 01:34:18PM -0800, Nitin Gupta wrote: On Wed, Jan 16, 2013 at 6:12 PM, Minchan Kim wrote: Lockdep complains about recursive deadlock of zram->init_lock. [1] made it false positive because we can't request IO to zram before setti

Re: [PATCH 3/3] zram: get rid of lockdep warning

2013-01-20 Thread Minchan Kim
On Fri, Jan 18, 2013 at 01:34:18PM -0800, Nitin Gupta wrote: > On Wed, Jan 16, 2013 at 6:12 PM, Minchan Kim wrote: > > Lockdep complains about recursive deadlock of zram->init_lock. > > [1] made it false positive because we can't request IO to zram > > before setting disksize. Anyway, we should sh

Re: [PATCH 3/3] zram: get rid of lockdep warning

2013-01-18 Thread Nitin Gupta
On Wed, Jan 16, 2013 at 6:12 PM, Minchan Kim wrote: > Lockdep complains about recursive deadlock of zram->init_lock. > [1] made it false positive because we can't request IO to zram > before setting disksize. Anyway, we should shut lockdep up to > avoid many reporting from user. > > This patch all

Re: [PATCH 3/3] zram: get rid of lockdep warning

2012-11-28 Thread Minchan Kim
On Wed, Nov 28, 2012 at 03:54:45PM +0100, Jerome Marchand wrote: > On 11/28/2012 03:35 AM, Minchan Kim wrote: > > Lockdep complains about recursive deadlock of zram->init_lock. > > [1] made it false positive because we can't request IO to zram > > before setting disksize. Anyway, we should shut loc

Re: [PATCH 3/3] zram: get rid of lockdep warning

2012-11-28 Thread Jerome Marchand
On 11/28/2012 03:35 AM, Minchan Kim wrote: > Lockdep complains about recursive deadlock of zram->init_lock. > [1] made it false positive because we can't request IO to zram > before setting disksize. Anyway, we should shut lockdep up to > avoid many reporting from user. > > This patch allocates zr