Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Jan Schmidt <mail@jan-o-sch.net>
To: Jan Schmidt <list.btrfs@jan-o-sch.net>
Cc: Mitch Harder <mitch.harder@sabayonlinux.org>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: NULL Pointer Dereference While Scrubbing
Date: Tue, 17 Jan 2012 17:42:31 +0100	[thread overview]
Message-ID: <4F15A4F7.50706@jan-o-sch.net> (raw)
In-Reply-To: <4F15A4A5.8040501@jan-o-sch.net>

On 17.01.2012 17:41, Jan Schmidt wrote:
> However, I'm not sure whether it's worth investigating any further, as
> the bug seems to be readahead-related which is presumably being replaced
> soon.

Ah, and it's solved anyway, so scratch that :-)

-Jan

  reply	other threads:[~2012-01-17 16:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03 17:35 NULL Pointer Dereference While Scrubbing Mitch Harder
2012-01-17  0:10 ` Mitch Harder
2012-01-17 16:35   ` Mitch Harder
2012-01-17 16:41     ` Jan Schmidt
2012-01-17 16:42       ` Jan Schmidt [this message]
2012-01-17 17:03       ` Mitch Harder
2012-01-17 17:08         ` Jan Schmidt

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=4F15A4F7.50706@jan-o-sch.net \
    --to=mail@jan-o-sch.net \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=list.btrfs@jan-o-sch.net \
    --cc=mitch.harder@sabayonlinux.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