From: Sasha Levin <levinsasha928@gmail.com>
To: Hugh Dickins <hughd@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
viro <viro@zeniv.linux.org.uk>,
oleg@redhat.com, "a.p.zijlstra" <a.p.zijlstra@chello.nl>,
mingo <mingo@kernel.org>, Dave Jones <davej@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Andrea Arcangeli <aarcange@redhat.com>
Subject: Re: mm: kernel BUG at mm/memory.c:1230
Date: Sun, 27 May 2012 22:45:28 +0200 [thread overview]
Message-ID: <CA+1xoqfGeQjrVWM3p4M0hV=hAwzx18bcoH7Bcn1mv_vOE8hDRw@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.00.1205261317310.2488@eggly.anvils>
On Sat, May 26, 2012 at 10:26 PM, Hugh Dickins <hughd@google.com> wrote:
> I'm keeping off the linux-next for the moment; I'll worry about this
> more if it shows up when we try 3.5-rc1. Your fuzzing tells that my
> logic above is wrong, but maybe it's just a passing defect in next.
I have a theory about this, which might explain it.
After a couple of days of not being able to reproduce it, I've decided
to revert Mel Gorman's patch related to memory corruption in mbind().
Once I've reverted it, I wasn't able to reproduce this exact case, but
did observe several other interesting things:
- The original mbind() memory corruption.
- Corruption in eventfd related structures (same dump as the mbind
one, but about eventfd structure).
- Same as above, but with flock.
- Hit a different BUG() in mm/mempolicy.c (The one at the end of slab_node()).
Is it possible that this issue could be explained by a corruption
related to the mbind() issue?
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-05-27 20:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 18:27 Sasha Levin
2012-05-24 19:07 ` Andrew Morton
2012-05-24 19:14 ` Sasha Levin
2012-05-26 20:26 ` Hugh Dickins
2012-05-26 23:54 ` Andrea Arcangeli
2012-05-27 20:45 ` Sasha Levin [this message]
2012-08-22 1:12 ` 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='CA+1xoqfGeQjrVWM3p4M0hV=hAwzx18bcoH7Bcn1mv_vOE8hDRw@mail.gmail.com' \
--to=levinsasha928@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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