From: Antoine Sirinelli <antoine@monte-stello.com>
To: Liu Bo <bo.li.liu@oracle.com>
Cc: Btrfs mailing list <linux-btrfs@vger.kernel.org>
Subject: Re: Oops with a "degraded" volume
Date: Mon, 17 Sep 2012 21:29:23 +0100 [thread overview]
Message-ID: <20120917202922.GA14962@speedy> (raw)
In-Reply-To: <5056C728.40606@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
On Mon, Sep 17, 2012 at 02:46:00PM +0800, Liu Bo wrote:
> On 09/15/2012 10:17 PM, Antoine Sirinelli wrote:
> > I have experienced a very reproducible Oops within the btrfs driver. On
> > a linux 3.5.4, if I mount a volume with the option "degraded" because
> > one of the device is missing, I would get an Oops when I unmount it (or
> > even before). You can see attached the kernel log.
>
> Thanks for the report. And this has been fixed by
>
> commit 99f5944b8477914406173b47b4f261356286730b
> Btrfs: do not strdup non existent strings
>
> You can find this commit in 3.6.0-rc5. :)
That's right, I have done the same test with rc6 and it does not crash
anymore.
Many thanks,
Antoine
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-09-17 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-15 14:17 Oops with a "degraded" volume Antoine Sirinelli
2012-09-17 6:46 ` Liu Bo
2012-09-17 20:29 ` Antoine Sirinelli [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=20120917202922.GA14962@speedy \
--to=antoine@monte-stello.com \
--cc=bo.li.liu@oracle.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;
as well as URLs for NNTP newsgroup(s).