The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.5-rc1 shm paging blocker
Date: Wed, 17 Mar 2004 16:43:14 +0100	[thread overview]
Message-ID: <20040317154314.GG2106@dualathlon.random> (raw)
In-Reply-To: <20040317061522.GN30940@dualathlon.random>

it seems the testing I did on 2.6.5-rc1 was incorrect (after testing
another 2 combinations of kernels were the problem exists I may have not
waited long enough while testing 2.6.5-rc1 for the first time and I
mistaken a sluggishness for a live lock and I clicked reboot too early,
that's the only reasonable explanation), it's working correctly now
(like it works fine with 2.6.5-rc1 - backout + objrmap + anon_vma so
it's impossible that it was my changes triggering it). If it happens
again I'll let you know. I still have to find what cause it in another
combinations of vm patches. Andrew, now that you've the testcase could
you test the -mm tree, and see if happens there, some -mm patch is one
of the diffs between the working tree and the non-working one.

However now I'll repeat all tests, if they works all flawlessy today I
will be very annoyed, since the thing was definitely not swapping at all
yesterday, no matter how long I awaited.

Now I start to wonder if kbuild may have screwed my kernel, effectively
it was a development tree, I don't run make distclean anymore in between
the kernel compiles (I almost don't feel the need of ccache anymoe ;),
but maybe I'm wrong trusting the buildsystem can be smart enough.

  parent reply	other threads:[~2004-03-17 15:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040317061522.GN30940@dualathlon.random>
2004-03-17  9:10 ` 2.4.5-rc1 shm paging blocker Andrew Morton
2004-03-17 15:43 ` Andrea Arcangeli [this message]
2004-03-17 21:19   ` Andrea Arcangeli

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=20040317154314.GG2106@dualathlon.random \
    --to=andrea@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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