linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: "J.H." <warthog9@kernel.org>
Cc: David Brown <davidb@codeaurora.org>,
	sedat.dilek@gmail.com, LKML <linux-kernel@vger.kernel.org>,
	linux-next@vger.kernel.org, ftpadmin@kernel.org,
	webmaster@kernel.org
Subject: Re: patchwork.kernel.org down
Date: Mon, 10 Jan 2011 12:53:20 -0800	[thread overview]
Message-ID: <adasjx07a67.fsf@cisco.com> (raw)
In-Reply-To: <4D2B664F.7050106@kernel.org> (J. H.'s message of "Mon, 10 Jan 2011 12:04:31 -0800")

 > I haven't added it to 20702 yet as I haven't had time to confirm if it's
 > the same issue, but at first glance it looks it.  My plan is to compile
 > up a mainline kernel, with the above patch, and with debugging turned on
 > and to capture as much as I can from that.

By the way, it is probably a good idea to boot with "slub_debug=FZP" to
make sure that slub debugging is turned on at runtime (unless you're
building at kernel with CONFIG_SLUB_DEBUG_ON=y, which I'm sure Fedora
doesn't do).  The crashes you're seeing definitely look like corruption
in the allocator.

 - R.

      parent reply	other threads:[~2011-01-10 20:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 20:12 patchwork.kernel.org down Sedat Dilek
2010-12-20 20:49 ` David Brown
2010-12-21  1:00   ` J.H.
2011-01-05 22:52     ` Roland Dreier
2011-01-05 23:48       ` Randy Dunlap
2011-01-06  2:58         ` Roland Dreier
2011-01-10 18:52       ` Roland Dreier
2011-01-10 20:04         ` J.H.
2011-01-10 20:33           ` Roland Dreier
2011-01-11  0:45             ` J.H.
2011-01-10 20:53           ` Roland Dreier [this message]

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=adasjx07a67.fsf@cisco.com \
    --to=rdreier@cisco.com \
    --cc=davidb@codeaurora.org \
    --cc=ftpadmin@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=warthog9@kernel.org \
    --cc=webmaster@kernel.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).