public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Bruce Guenter <bruce@untroubled.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: Cross-subvolume link causes kernel BUG
Date: Mon, 8 Mar 2010 12:26:56 -0600	[thread overview]
Message-ID: <20100308182656.GA7102@untroubled.org> (raw)
In-Reply-To: <m3hboqsof9.fsf@pullcord.laptop.org>

[-- Attachment #1: Type: text/plain, Size: 430 bytes --]

On Mon, Mar 08, 2010 at 12:39:38PM -0500, Chris Ball wrote:
> I think this is fixed in 2.6.33, as a result of the patch below.
> Let us know if you see a segfault on 2.6.33, or after applying this
> patch to your current kernel.

This patch does fix the problem for 2.6.32.9, thanks.  Has this patch
been submitted for the 2.6.32.y series?

-- 
Bruce Guenter <bruce@untroubled.org>                http://untroubled.org/

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-03-08 18:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-08 17:24 Cross-subvolume link causes kernel BUG Bruce Guenter
2010-03-08 17:39 ` Chris Ball
2010-03-08 18:26   ` Bruce Guenter [this message]
2010-03-08 21:21     ` Mike Fedyk
2010-03-09  2:16       ` Mike Fedyk

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=20100308182656.GA7102@untroubled.org \
    --to=bruce@untroubled.org \
    --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