public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Elladan <elladan@eskimo.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Kernel oops with 2.6.31 in btrfs_set_acl
Date: Fri, 18 Sep 2009 16:50:11 -0400	[thread overview]
Message-ID: <m3ws3wasfw.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <20090918144353.GA9761@eskimo.com> (elladan@eskimo.com's message of "Fri, 18 Sep 2009 07:43:53 -0700")

Hi,

   > Hi, I got an oops this morning with btrfs on the Ubuntu 2.6.31
   > kernel.  I mounted with compress and thread_pool=4.  This is on a
   > 64 bit quad AMD machine.
   > 
   > [614439.132228] [<ffffffffa0f3c157>] ? btrfs_set_acl+0x87/0x230

Could you tell us what line of the source code that is?  This should
work, after gdb btrfs.ko:

(gdb) list *btrfs_set_acl+0x87

- Chris.
-- 
Chris Ball   <cjb@laptop.org>
One Laptop Per Child

      reply	other threads:[~2009-09-18 20:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-18 14:43 Kernel oops with 2.6.31 in btrfs_set_acl Elladan
2009-09-18 20:50 ` Chris Ball [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=m3ws3wasfw.fsf@pullcord.laptop.org \
    --to=cjb@laptop.org \
    --cc=elladan@eskimo.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