From: Dave Jones <davej@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Konstantin Khlebnikov <khlebnikov@openvz.org>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: a whole bunch of crashes since todays -mm merge.
Date: Thu, 7 Jun 2012 22:22:41 -0400 [thread overview]
Message-ID: <20120608022240.GC7191@redhat.com> (raw)
In-Reply-To: <CA+55aFz12eeNHGt5GV_w=brPVed3Ga9HjYy73dbusEyPpX39OQ@mail.gmail.com>
On Thu, Jun 07, 2012 at 06:09:20PM -0700, Linus Torvalds wrote:
> On Thu, Jun 7, 2012 at 6:05 PM, Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > It appears this is due to me fat-fingering conflict resolution last
> > week. That hunk is supposed to be in mm_release(), not mmput().
>
> Ahh. That would indeed make more sense. The mmput() placement is
> insane for so many reasons.
>
> I reverted it and pushed it out, because it clearly was horrible. Even
> if it is possible that Dave's problems are due to something else (but
> if they started with the mm merge, I don't see anything else nearly as
> scary in there)
Spooky. With that reverted, I don't see those weird oopses any more,
even with the potentially suspect 8169 tracing patch reapplied. So uh, I dunno.
Dave
--
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>
next prev parent reply other threads:[~2012-06-08 2:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 0:24 a whole bunch of crashes since todays -mm merge Dave Jones
2012-06-08 0:52 ` Linus Torvalds
2012-06-08 1:00 ` Dave Jones
2012-06-08 1:06 ` Linus Torvalds
2012-06-08 1:12 ` Dave Jones
2012-06-08 1:25 ` Linus Torvalds
2012-06-08 1:05 ` Andrew Morton
2012-06-08 1:09 ` Linus Torvalds
2012-06-08 2:22 ` Dave Jones [this message]
2012-06-08 1:39 ` Stephen Rothwell
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=20120608022240.GC7191@redhat.com \
--to=davej@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=khlebnikov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oleg@redhat.com \
--cc=torvalds@linux-foundation.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).