From: Jens Axboe <jens.axboe@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-kernel@vger.kernel.org, linux-mm@vger.kernel.org
Subject: Re: oops in __bounce_end_io_read under kvm
Date: Sun, 28 Dec 2008 19:25:00 +0100 [thread overview]
Message-ID: <20081228182459.GX32491@kernel.dk> (raw)
In-Reply-To: <20081228181948.GA23568@lst.de>
On Sun, Dec 28 2008, Christoph Hellwig wrote:
> On Sun, Dec 28, 2008 at 07:10:59PM +0100, Jens Axboe wrote:
> > Is this -rc9 stock + xfs patches, or does it include -mm or -next
> > patches (or the block patches)?
>
> Just -rc9 and xfs updates. The only change outside of fs/xfs/ is a new
> define in fs.h and a couple new helpers in inode.c
OK, then it's surely a new bug. Could you do a gdb l *0xbla on that
address to check where it's faulting?
--
Jens Axboe
next prev parent reply other threads:[~2008-12-28 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-26 17:36 oops in __bounce_end_io_read under kvm Christoph Hellwig
2008-12-28 18:10 ` Jens Axboe
2008-12-28 18:19 ` Christoph Hellwig
2008-12-28 18:25 ` Jens Axboe [this message]
2009-01-01 21:08 ` Christoph Hellwig
2009-01-12 20:30 ` Christoph Hellwig
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=20081228182459.GX32491@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@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