From: Chris Mason <chris.mason@oracle.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Jens Axboe <jens.axboe@oracle.com>,
Sven Wegener <sven.wegener@stealer.net>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Add compability for kernels >=2.6.27-rc1
Date: Thu, 31 Jul 2008 15:37:38 -0400 [thread overview]
Message-ID: <1217533058.20239.62.camel@think.oraclecorp.com> (raw)
In-Reply-To: <1217532421.3454.291.camel@pmac.infradead.org>
On Thu, 2008-07-31 at 20:27 +0100, David Woodhouse wrote:
> On Wed, 2008-07-30 at 16:43 -0400, Chris Mason wrote:
> > On Wed, 2008-07-30 at 22:13 +0200, Jens Axboe wrote:
> >
> > [ rcu page cache ]
> >
> > > > > For btrfs's usage, it should be safe with a simple rcu_read_lock(), if
> > > > > the return is referenced safely.
> > > > >
> > > >
> > > > This btrfs code is basically a find_get_page without the get. It should
> > > > only be called when I know I already have a reference on the page.
> > >
> > > Then it's definitely safe ;-)
> > >
> >
> > Yeah, I'm testing on the latest git now and it all seems ok. I'll push
> > this out, thanks Sven.
>
> Seems to crash for me with Linus' current tree. I thought it was
> something to do with my fixes for NFS export, but now I've hooked up a
> serial console and managed to catch it, I suspect not...
>
> BUG: unable to handle kernel paging request at ffff880107c2aa00
> IP: [<ffffffffa03e73bc>] end_bio_extent_writepage+0x1f4/0x29c [btrfs]
If you can reliably reproduce this, please try with the spin locks
instead of rcu read locks. What were you doing at the time?
-chris
next prev parent reply other threads:[~2008-07-31 19:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 19:11 [PATCH] Add compability for kernels >=2.6.27-rc1 Sven Wegener
2008-07-30 19:56 ` Jens Axboe
2008-07-30 20:11 ` Chris Mason
2008-07-30 20:13 ` Jens Axboe
2008-07-30 20:43 ` Chris Mason
2008-07-31 19:27 ` David Woodhouse
2008-07-31 19:37 ` Chris Mason [this message]
2008-07-31 19:52 ` David Woodhouse
2008-08-19 14:51 ` David Woodhouse
2008-08-19 16:30 ` Chris Mason
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=1217533058.20239.62.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=dwmw2@infradead.org \
--cc=jens.axboe@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sven.wegener@stealer.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.