From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: recent bdi changes result in WARN_ON on luksClose / dm
Date: Sun, 13 Sep 2009 11:13:37 +0200 [thread overview]
Message-ID: <20090913091337.GA21969@Chamillionaire.breakpoint.cc> (raw)
In-Reply-To: <20090912195839.GG14984@kernel.dk>
* 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
|[<c0028dd8>] (unwind_backtrace+0x0/0xdc) from [<c003adb0>] (warn_slowpath_common+0x4c/0x80)
|[<c003adb0>] (warn_slowpath_common+0x4c/0x80) from [<c00b0998>] (writeback_inodes_wb+0x2cc/0x49c)
|[<c00b0998>] (writeback_inodes_wb+0x2cc/0x49c) from [<c00b0c98>] (wb_writeback+0x130/0x180)
|[<c00b0c98>] (wb_writeback+0x130/0x180) from [<c00b10f8>] (wb_do_writeback+0x7c/0x1d0)
|[<c00b10f8>] (wb_do_writeback+0x7c/0x1d0) from [<c00b1284>] (bdi_writeback_task+0x38/0xb0)
|[<c00b1284>] (bdi_writeback_task+0x38/0xb0) from [<c007f788>] (bdi_start_fn+0x74/0xe0)
|[<c007f788>] (bdi_start_fn+0x74/0xe0) from [<c004f2cc>] (kthread+0x7c/0x84)
|[<c004f2cc>] (kthread+0x7c/0x84) from [<c0024858>] (kernel_thread_exit+0x0/0x8)
|---[ end trace e1f395241bdb07ff ]---
Sebastian
next prev parent reply other threads:[~2009-09-13 9:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-12 11:19 Sebastian Andrzej Siewior
2009-09-12 19:52 ` Jens Axboe
2009-09-12 19:58 ` Jens Axboe
2009-09-12 20:07 ` Jens Axboe
2009-09-13 9:13 ` Sebastian Andrzej Siewior [this message]
2009-09-13 17:57 ` Jens Axboe
2009-09-14 9:05 ` Jens Axboe
2009-09-14 12:27 ` Sebastian Andrzej Siewior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090913091337.GA21969@Chamillionaire.breakpoint.cc \
--to=sebastian@breakpoint.cc \
--cc=dm-devel@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®