linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Nikhilesh Reddy <reddyn@codeaurora.org>
Cc: linux-ext4@vger.kernel.org, "Darrick J. Wong" <darrick.wong@oracle.com>
Subject: Re: Writes blocked on wait_for_stable_page (Writes of less than page size sometimes take too long)
Date: Wed, 4 Feb 2015 12:02:51 -0500	[thread overview]
Message-ID: <20150204170251.GG2509@thunk.org> (raw)
In-Reply-To: <54D15F0D.6030109@codeaurora.org>

On Tue, Feb 03, 2015 at 03:51:41PM -0800, Nikhilesh Reddy wrote:
> >
> >I won't give any warrantees, of course, since the AOSP kernel doesn't
> >build on x86 and so I can't easily run regression tests on it.  So if
> >it breaks, you will get to keep both pieces.  I will try to at least
> >look at bug reports, though, and I can say that 3.18 backport on the
> >stock 3.10 kernel survives xfstests much better than the 3.10 version
> >of ext4, since a modern xfstests very quickly caused the stock 3.10
> >kernel to panic.  :-)

Note: I managed to patch/bludgeon the AOSP kernel so it will build on
x86 (apparently some Nvidia engineers wasn't very careful about adding
Tegra support without breaking x86 builds, boo hiss), and so I was
able to run a quick smoke test using kvm-xfstests.  "kvm-xfstests
smoke" runs most of the tests successfully, modulo a few expected
failures, but then the kernel locks up after executing "echo 3 >
/proc/sys/vm/drop_caches; cat /proc/slabinfo" in the test framework,
which happens just before it halts the VM.

I suspect there is a bug in my commit (f9f56f19dc) which lets ext4 use
the older shrinker API which is used by the 3.10 kernel.  It's on my
todo list to look at, but I'm in Mountain View this week and my time
has been almost toally sucked up by meetings, so I haven't gotten to
it yet.

So in case you end up doing some testing of the 3.10 backport branch,
I thought I should give you a quick heads up.

Cheers,

						- Ted

      reply	other threads:[~2015-02-04 17:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-28 18:58 Writes blocked on wait_for_stable_page (Writes of less than page size sometimes take too long) Nikhilesh Reddy
2015-01-28 19:27 ` Nikhilesh Reddy
2015-01-28 21:39   ` Darrick J. Wong
2015-01-28 23:23     ` Nikhilesh Reddy
2015-01-28 23:36       ` Nikhilesh Reddy
2015-01-28 23:57         ` Darrick J. Wong
2015-01-30 21:25           ` Nikhilesh Reddy
2015-01-30 21:53             ` Darrick J. Wong
2015-02-01  2:37           ` Theodore Ts'o
2015-02-03 23:51             ` Nikhilesh Reddy
2015-02-04 17:02               ` Theodore Ts'o [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=20150204170251.GG2509@thunk.org \
    --to=tytso@mit.edu \
    --cc=darrick.wong@oracle.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=reddyn@codeaurora.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;
as well as URLs for NNTP newsgroup(s).