From: Sebastian Andrzej Siewior Subject: Re: recent bdi changes result in WARN_ON on luksClose / dm Date: Sun, 13 Sep 2009 11:13:37 +0200 Message-ID: <20090913091337.GA21969@Chamillionaire.breakpoint.cc> References: <20090912111928.GA8013@Chamillionaire.breakpoint.cc> <20090912195212.GF14984@kernel.dk> <20090912195839.GG14984@kernel.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Return-path: Content-Disposition: inline In-Reply-To: <20090912195839.GG14984@kernel.dk> Sender: linux-kernel-owner@vger.kernel.org To: Jens Axboe Cc: dm-devel@redhat.com, linux-kernel@vger.kernel.org List-Id: dm-devel.ids * Jens Axboe | 2009-09-12 21:58:40 [+0200]: >Don't count this as a real fix, I'll investigate closer on monday. Does >the warning go away with this hack? It'll ensure that pending dirty >inodes are flushed. That warning goes away but another pops up: |------------[ cut here ]------------ |WARNING: at /home/bigeasy/git/cryptodev-2.6/fs/fs-writeback.c:504 writeback_inodes_wb+0x2cc/0x49c() |Modules linked in: sha256_generic cbc dm_crypt |[] (unwind_backtrace+0x0/0xdc) from [] (warn_slowpath_common+0x4c/0x80) |[] (warn_slowpath_common+0x4c/0x80) from [] (writeback_inodes_wb+0x2cc/0x49c) |[] (writeback_inodes_wb+0x2cc/0x49c) from [] (wb_writeback+0x130/0x180) |[] (wb_writeback+0x130/0x180) from [] (wb_do_writeback+0x7c/0x1d0) |[] (wb_do_writeback+0x7c/0x1d0) from [] (bdi_writeback_task+0x38/0xb0) |[] (bdi_writeback_task+0x38/0xb0) from [] (bdi_start_fn+0x74/0xe0) |[] (bdi_start_fn+0x74/0xe0) from [] (kthread+0x7c/0x84) |[] (kthread+0x7c/0x84) from [] (kernel_thread_exit+0x0/0x8) |---[ end trace e1f395241bdb07ff ]--- Sebastian