From: Minchan Kim <minchan@kernel.org>
To: Dhaval Giani <dgiani@mozilla.com>
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?)
Date: Wed, 19 Jun 2013 13:41:47 +0900 [thread overview]
Message-ID: <20130619044147.GC10961@bbox> (raw)
In-Reply-To: <51C091D6.8010608@mozilla.com>
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?
FYI: John, Dhaval
I am working to clean purging mess up so maybe it would need not a few
change for purging part.
Thanks!
--
Kind regards,
Minchan Kim
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Minchan Kim <minchan@kernel.org>
To: Dhaval Giani <dgiani@mozilla.com>
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?)
Date: Wed, 19 Jun 2013 13:41:47 +0900 [thread overview]
Message-ID: <20130619044147.GC10961@bbox> (raw)
In-Reply-To: <51C091D6.8010608@mozilla.com>
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?
FYI: John, Dhaval
I am working to clean purging mess up so maybe it would need not a few
change for purging part.
Thanks!
--
Kind regards,
Minchan Kim
next prev parent reply other threads:[~2013-06-19 4:41 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 4:22 [PATCH 0/8] Volatile Ranges (v8?) John Stultz
2013-06-12 4:22 ` John Stultz
2013-06-12 4:22 ` [PATCH 1/8] vrange: Add basic data structure and functions John Stultz
2013-06-12 4:22 ` John Stultz
2013-06-12 4:22 ` [PATCH 2/8] vrange: Add vrange support for file address_spaces John Stultz
2013-06-12 4:22 ` John Stultz
2013-06-12 4:22 ` [PATCH 3/8] vrange: Add vrange support to mm_structs John Stultz
2013-06-12 4:22 ` John Stultz
2013-06-12 4:22 ` [PATCH 4/8] vrange: Clear volatility on new mmaps John Stultz
2013-06-12 4:22 ` John Stultz
2013-06-13 6:28 ` Minchan Kim
2013-06-13 6:28 ` Minchan Kim
2013-06-13 23:43 ` John Stultz
2013-06-13 23:43 ` John Stultz
2013-06-14 0:21 ` Minchan Kim
2013-06-14 0:21 ` Minchan Kim
2013-06-12 4:22 ` [PATCH 5/8] vrange: Add new vrange(2) system call John Stultz
2013-06-12 4:22 ` John Stultz
2013-06-12 6:48 ` NeilBrown
2013-06-12 18:47 ` John Stultz
2013-06-12 18:47 ` John Stultz
2013-06-20 21:05 ` Dhaval Giani
2013-06-20 21:05 ` Dhaval Giani
2013-06-12 4:22 ` [PATCH 6/8] vrange: Add GFP_NO_VRANGE allocation flag John Stultz
2013-06-12 4:22 ` John Stultz
2013-06-12 4:22 ` [PATCH 7/8] vrange: Add method to purge volatile ranges John Stultz
2013-06-12 4:22 ` John Stultz
2013-06-17 7:13 ` Minchan Kim
2013-06-17 7:13 ` Minchan Kim
2013-06-17 7:24 ` Minchan Kim
2013-06-17 7:24 ` Minchan Kim
2013-06-19 4:34 ` Minchan Kim
2013-06-19 4:34 ` Minchan Kim
2013-10-01 14:00 ` Krzysztof Kozlowski
2013-10-02 1:32 ` Minchan Kim
2013-06-12 4:22 ` [PATCH 8/8] vrange: Send SIGBUS when user try to access purged page John Stultz
2013-06-12 4:22 ` John Stultz
2013-06-19 4:36 ` Minchan Kim
2013-06-19 4:36 ` Minchan Kim
2013-06-17 16:24 ` [PATCH 0/8] Volatile Ranges (v8?) Dhaval Giani
2013-06-18 4:11 ` Minchan Kim
2013-06-18 4:11 ` Minchan Kim
2013-06-18 16:59 ` Dhaval Giani
2013-06-18 16:59 ` Dhaval Giani
2013-06-19 4:41 ` Minchan Kim [this message]
2013-06-19 4:41 ` Minchan Kim
2013-06-19 18:36 ` Dhaval Giani
2013-06-19 18:36 ` Dhaval Giani
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=20130619044147.GC10961@bbox \
--to=minchan@kernel.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andrea@betterlinux.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=dave@linux.vnet.ibm.com \
--cc=david@fromorbit.com \
--cc=dgiani@mozilla.com \
--cc=dmitry.adamushko@gmail.com \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=john.stultz@linaro.org \
--cc=kernel-team@android.com \
--cc=kosaki.motohiro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=mh@glandium.org \
--cc=neilb@suse.de \
--cc=riel@redhat.com \
--cc=rlove@google.com \
--cc=tglek@mozilla.com \
--cc=walken@google.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 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.