From: Chris Mason <chris.mason@oracle.com>
To: Lukas Vacek <pheeror@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: umount oops
Date: Fri, 25 Jul 2008 08:43:33 -0400 [thread overview]
Message-ID: <1216989813.7572.19.camel@think.oraclecorp.com> (raw)
In-Reply-To: <11129bee0807250414p7f28a4daxa3cd49c1bcd983c2@mail.gmail.com>
On Fri, 2008-07-25 at 13:14 +0200, Lukas Vacek wrote:
> sorry, I made a typo in the "testcase" (the second mount)
> Basically, it might be enough to mount two different btrfs filesystems
> to two different locations, umount one of them and watch
> /var/log/kern.log for the oops
>
Thanks for this bug report, which Btrfs version was in use?
-chris
next prev parent reply other threads:[~2008-07-25 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 21:13 umount oops Lukas Vacek
2008-07-25 11:14 ` Lukas Vacek
2008-07-25 12:43 ` Chris Mason [this message]
2008-07-25 13:54 ` Lukas Vacek
2008-07-25 14:08 ` Chris Mason
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=1216989813.7572.19.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=pheeror@gmail.com \
/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.