From: Josef Bacik <josef@redhat.com>
To: Johannes Hirte <johannes.hirte@fem.tu-ilmenau.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Oops with enospc-branch
Date: Mon, 14 Sep 2009 11:42:23 -0400 [thread overview]
Message-ID: <20090914154222.GA25833@localhost.localdomain> (raw)
In-Reply-To: <200909141326.48354.johannes.hirte@fem.tu-ilmenau.de>
On Mon, Sep 14, 2009 at 01:26:48PM +0200, Johannes Hirte wrote:
> With the enospc-branch my system oops with some workload. Netconsole gave me
> this trace:
>
Thank you for reporting this. I'm able to reproduce it here and am working on a
fix. Thanks,
Josef
prev parent reply other threads:[~2009-09-14 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 11:26 Oops with enospc-branch Johannes Hirte
2009-09-14 15:42 ` 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=20090914154222.GA25833@localhost.localdomain \
--to=josef@redhat.com \
--cc=johannes.hirte@fem.tu-ilmenau.de \
--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