From: Jens Axboe <jens.axboe@oracle.com>
To: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
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 19:57:17 +0200 [thread overview]
Message-ID: <20090913175717.GO14984@kernel.dk> (raw)
In-Reply-To: <20090913091337.GA21969@Chamillionaire.breakpoint.cc>
On Sun, Sep 13 2009, Sebastian Andrzej Siewior wrote:
> * 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:
Oh right, just goes to show that it's doing this backwards. We need the
umount rwsem for WB_SYNC_ALL. I'll look at this tomorrow.
--
Jens Axboe
next prev parent reply other threads:[~2009-09-13 17:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-12 11:19 recent bdi changes result in WARN_ON on luksClose / dm 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
2009-09-13 17:57 ` Jens Axboe [this message]
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=20090913175717.GO14984@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian@breakpoint.cc \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.