From: Christoph Hellwig <hch@infradead.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: reproducible xfs/vmap oops
Date: Wed, 4 Feb 2009 03:30:37 -0500 [thread overview]
Message-ID: <20090204083037.GA17493@infradead.org> (raw)
In-Reply-To: <20090204081547.GA21487@infradead.org>
On Wed, Feb 04, 2009 at 03:15:47AM -0500, Christoph Hellwig wrote:
> On Wed, Feb 04, 2009 at 04:48:55PM +1100, Nick Piggin wrote:
> > OK, I could reproduce this directly with a vmap test. With this patch,
> > I'm no longer able to. (not sure how this mail client goes with attaching
> > patches, sorry if it messes up)
>
> With that patch applies I run into a different issue:
And later on we run out of vmalloc space a lot getting warnings like
this:
[ 5796.986579] vmap allocation for size 4194304 failed: use
vmalloc=<size> to increase size.
[ 5797.008728] xfs_buf_get_noaddr: failed to map pages
This didn't happen before. Maybe it's a result of some of the more
lazy TLB flushing?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-02-04 8:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 8:12 reproducible xfs/vmap oops Christoph Hellwig
2009-02-01 16:14 ` Christoph Hellwig
2009-02-03 15:51 ` Christoph Hellwig
[not found] ` <200902040303.13933.nickpiggin@yahoo.com.au>
2009-02-03 16:05 ` Christoph Hellwig
2009-02-03 18:44 ` Christoph Hellwig
2009-02-03 21:04 ` Christoph Hellwig
2009-02-03 21:42 ` Dave Chinner
2009-02-03 21:47 ` Christoph Hellwig
2009-02-03 22:08 ` Christoph Hellwig
[not found] ` <200902041648.55603.nickpiggin@yahoo.com.au>
2009-02-04 8:15 ` Christoph Hellwig
2009-02-04 8:30 ` Christoph Hellwig [this message]
[not found] ` <200902042027.40762.nickpiggin@yahoo.com.au>
2009-02-04 19:38 ` Christoph Hellwig
[not found] ` <200902101543.15988.nickpiggin@yahoo.com.au>
2009-02-10 7:54 ` Christoph Hellwig
2009-02-15 19:15 ` 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=20090204083037.GA17493@infradead.org \
--to=hch@infradead.org \
--cc=nickpiggin@yahoo.com.au \
--cc=xfs@oss.sgi.com \
/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