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: Tue, 19 Aug 2008 12:30:05 -0400 [thread overview]
Message-ID: <20080819162619.GA14618@think.oraclecorp.com> (raw)
In-Reply-To: <1219157500.3184.484.camel@pmac.infradead.org>
On Tue, Aug 19, 2008 at 03:51:40PM +0100, David Woodhouse wrote:
> On Thu, 2008-07-31 at 15:37 -0400, Chris Mason wrote:
> > > 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?
>
> Just using CONFIG_DEBUG_PAGEALLOC and dirtying a bunch of pages from
> different inodes seems enough. Another patch to add to my collection at
> git.infradead.org/users/dwmw2/btrfs-kernel-unstable.git ...
Great, I'm testing this locally, it should solve Toei Rei's oopsen. It
doesn't solve the missing checksum errors that Steve was hitting, but
I'm able to trigger those locally now and hope to nail them down
today.
-chris
prev parent reply other threads:[~2008-08-19 16:30 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
2008-07-31 19:52 ` David Woodhouse
2008-08-19 14:51 ` David Woodhouse
2008-08-19 16:30 ` Chris Mason [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=20080819162619.GA14618@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox