From: Josef Bacik <jbacik@redhat.com>
To: Josef Bacik <jbacik@redhat.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] create/destroy io workqueues on module init/exit
Date: Mon, 16 Jun 2008 14:01:18 -0400 [thread overview]
Message-ID: <20080616180118.GA19121@unused.rdu.redhat.com> (raw)
In-Reply-To: <20080616175423.GA17364@unused.rdu.redhat.com>
On Mon, Jun 16, 2008 at 01:54:23PM -0400, Josef Bacik wrote:
> Hello,
>
> Theres a problem with btrfs where if you have more than one btrfs fs's mounted,
> if you unmount one of the fs's, and then do some work on the other fs, the box
> will panic. This is because in close_ctree() we destroy the two global io
> workqueues, even though we're still using them for the other fs. This patch
> moves the creation/destruction of the workqueues to the init/exit parts of the
> btrfs module. I tested with this patch and my panic went away. Thanks,
>
> Signed-off-by: Josef Bacik <jbacik@redhat.com>
>
>
Hmm sorry I pulled down the stable repo, not the unstable, ignore this.
Josef
prev parent reply other threads:[~2008-06-16 18:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 17:54 [PATCH] create/destroy io workqueues on module init/exit Josef Bacik
2008-06-16 18:01 ` Josef Bacik [this message]
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=20080616180118.GA19121@unused.rdu.redhat.com \
--to=jbacik@redhat.com \
--cc=linux-btrfs@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