All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: oops in __bounce_end_io_read under kvm
Date: Thu, 1 Jan 2009 22:08:31 +0100	[thread overview]
Message-ID: <20090101210831.GA20419@lst.de> (raw)
In-Reply-To: <20081228182459.GX32491@kernel.dk>

On Sun, Dec 28, 2008 at 07:25:00PM +0100, Jens Axboe wrote:
> 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?

It took a while to reproduce it again, but I got it again today.


(gdb) l *0xc01a5444
0xc01a5444 is in __bounce_end_io_read
(/home/hch/work/xfs/arch/x86/include/asm/string_32.h:35).
30	extern size_t strlen(const char *s);
31	
32	static __always_inline void *__memcpy(void *to, const void *from, size_t n)
33	{
34		int d0, d1, d2;
35		asm volatile("rep ; movsl\n\t"
36			     "movl %4,%%ecx\n\t"
37			     "andl $3,%%ecx\n\t"
38			     "jz 1f\n\t"
39			     "rep ; movsb\n\t"


  reply	other threads:[~2009-01-01 21:08 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
2009-01-01 21:08       ` Christoph Hellwig [this message]
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=20090101210831.GA20419@lst.de \
    --to=hch@lst.de \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@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 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.