public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jack Steiner <steiner@sgi.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	rusty@rustcorp.com.au, sfr@canb.auug.org.au,
	linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH] - Updated: Fix slab corruption caused by alloc_cpumask_var_node()
Date: Fri, 3 Apr 2009 00:23:59 +0200	[thread overview]
Message-ID: <20090402222359.GE9239@elte.hu> (raw)
In-Reply-To: <20090402220900.GA15129@sgi.com>


* Jack Steiner <steiner@sgi.com> wrote:

> Fix slab corruption caused by alloc_cpumask_var_node() overwriting
> the tail end of an off-stack cpumask.
> 
> The function zeros out cpumask bits beyond the last possible cpu.
> The starting point for zeroing should be the beginning
> of the mask offset by a byte count derived from the number
> of possible cpus. The offset was calculated in bits instead of bytes.
> This resulted in overwriting the end of the cpumask.
> 
> 
> v2.6.29 is also affected by this bug.
> 
> 
> Signed-off-by: Jack Steiner <steiner@sgi.com>
> Acked-by: Mike Travis <travis.sgi.com>
> Acked-by: Ingo Molnar <mingo@elte.hu>

In the future you can add:

  Cc: <stable@kernel.org>

to the signoff/ack section of the changlog in such cases - then the 
-stable folks will notice the commit automatically.

Thanks,

	Ingo

  reply	other threads:[~2009-04-02 22:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-02 21:27 [PATCH] - Fix slab corruption caused by alloc_cpumask_var_node() Jack Steiner
2009-04-02 21:39 ` Andrew Morton
2009-04-02 22:09   ` [PATCH] - Updated: " Jack Steiner
2009-04-02 22:23     ` Ingo Molnar [this message]
2009-04-02 21:42 ` [PATCH] - " Ingo Molnar
2009-04-05  5:31   ` Rusty Russell

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=20090402222359.GE9239@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=sfr@canb.auug.org.au \
    --cc=stable@kernel.org \
    --cc=steiner@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox