Message-ID: <51C1FA48.2000401@mozilla.com>
Date: Wed, 19 Jun 2013 14:36:56 -0400
From: Dhaval Giani <dgiani@mozilla.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Minchan Kim <minchan@kernel.org>
CC: John Stultz <john.stultz@linaro.org>, LKML <linux-kernel@vger.kernel.org>,
        Andrew Morton <akpm@linux-foundation.org>,
        Android Kernel Team <kernel-team@android.com>,
        Robert Love <rlove@google.com>, Mel Gorman <mel@csn.ul.ie>,
        Hugh Dickins <hughd@google.com>, Dave Hansen <dave@linux.vnet.ibm.com>,
        Rik van Riel <riel@redhat.com>,
        Dmitry Adamushko <dmitry.adamushko@gmail.com>,
        Dave Chinner <david@fromorbit.com>, Neil Brown <neilb@suse.de>,
        Andrea Righi <andrea@betterlinux.com>,
        Andrea Arcangeli <aarcange@redhat.com>,
        "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
        Mike Hommey <mh@glandium.org>, Taras Glek <tglek@mozilla.com>,
        Jan Kara <jack@suse.cz>, KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
        Michel Lespinasse <walken@google.com>,
        "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH 0/8] Volatile Ranges (v8?)
References: <1371010971-15647-1-git-send-email-john.stultz@linaro.org> <51BF3827.4060606@mozilla.com> <20130618041100.GA3116@bbox> <51C091D6.8010608@mozilla.com> <20130619044147.GC10961@bbox>
In-Reply-To: <20130619044147.GC10961@bbox>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1973
Lines: 52

On 2013-06-19 12:41 AM, Minchan Kim wrote:
> Hello Dhaval,
>
> On Tue, Jun 18, 2013 at 12:59:02PM -0400, Dhaval Giani wrote:
>> On 2013-06-18 12:11 AM, Minchan Kim wrote:
>>> Hello Dhaval,
>>>
>>> On Mon, Jun 17, 2013 at 12:24:07PM -0400, Dhaval Giani wrote:
>>>> Hi John,
>>>>
>>>> I have been giving your git tree a whirl, and in order to simulate a
>>>> limited memory environment, I was using memory cgroups.
>>>>
>>>> The program I was using to test is attached here. It is your test
>>>> code, with some changes (changing the syscall interface, reducing
>>>> the memory pressure to be generated).
>>>>
>>>> I trapped it in a memory cgroup with 1MB memory.limit_in_bytes and hit this,
>>>>
>>>> [  406.207612] ------------[ cut here ]------------
>>>> [  406.207621] kernel BUG at mm/vrange.c:523!
>>>> [  406.207626] invalid opcode: 0000 [#1] SMP
>>>> [  406.207631] Modules linked in:
>>>> [  406.207637] CPU: 0 PID: 1579 Comm: volatile-test Not tainted
>>> Thanks for the testing!
>>> Does below patch fix your problem?
>> Yes it does! Thank you very much for the patch.
> Thaks for the confirming.
> While I tested it, I found several problems so I just sent fixes as reply
> of each [7/8] and [8/8].
> Could you test it?

Great! These patches (seem to) fix another issue I noticed yesterday 
with signal handling. I have pushed out my code for testing this stuff 
at https://github.com/volatile-ranges-test/vranges-test . The code and 
the scripts are still unpolished (as in you don't get a pass or fail) 
but they seem to work just fine.

>
> FYI: John, Dhaval
>
> I am working to clean purging mess up so maybe it would need not a few
> change for purging part.

Great, I will also take a look at the code.

Dhaval
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/