Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev <netdev@vger.kernel.org>
Subject: net-next currently not in good shape
Date: Wed, 08 May 2013 16:30:25 -0700	[thread overview]
Message-ID: <1368055825.13473.31.camel@edumazet-glaptop> (raw)

Hi David

net-next is currently lacking following patch and dies at boot time (at
leat on my machines)

This message might help others.

Thanks !


commit 956e46efb2478ebff7a871138458fa8124fd18dd
Author: Chris Mason <clmason@fusionio.com>
Date:   Wed May 8 15:56:28 2013 -0400

    mm/slab: Fix crash during slab init
    
    Commit 8a965b3baa89 ("mm, slab_common: Fix bootstrap creation of kmalloc
    caches") introduced a regression that caused us to crash early during
    boot.  The commit was introducing ordering of slab creation, making sure
    two odd-sized slabs were created after specific powers of two sizes.
    
    But, if any of the power of two slabs were created earlier during boot,
    slabs at index 1 or 2 might not get created at all.  This patch makes
    sure none of the slabs get skipped.
    
    Tony Lindgren bisected this down to the offending commit, which really
    helped because bisect kept bringing me to almost but not quite this one.
    
    Signed-off-by: Chris Mason <chris.mason@fusionio.com>
    Acked-by: Christoph Lameter <cl@linux.com>
    Acked-by: Tony Lindgren <tony@atomide.com>
    Acked-by: Soren Brinkmann <soren.brinkmann@xilinx.com>
    Tested-by: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
    Tested-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

             reply	other threads:[~2013-05-08 23:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-08 23:30 Eric Dumazet [this message]
2013-05-09  0:57 ` net-next currently not in good shape David Miller

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=1368055825.13473.31.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.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