public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: James Jones <jajones@nvidia.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: Fix find_next_zero_bit and related assembly
Date: Wed, 24 Nov 2010 19:15:04 +0000	[thread overview]
Message-ID: <20101124191504.GC13934@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.00.1011241412250.9313@xanadu.home>

On Wed, Nov 24, 2010 at 02:13:05PM -0500, Nicolas Pitre wrote:
> On Wed, 24 Nov 2010, James Jones wrote:
> 
> > On Wednesday 24 November 2010 11:00:12 am Nicolas Pitre wrote:
> > > On Wed, 24 Nov 2010, Stephen Boyd wrote:
> > > > On 11/23/2010 03:28 PM, James Jones wrote:
> > > > > On Tuesday 23 November 2010 13:26:47 Nicolas Pitre wrote:
> > > > >> On Thu, 11 Nov 2010, James Jones wrote:
> > > > >>> The find_next_bit, find_first_bit, find_next_zero_bit
> > > > >>> and find_first_zero_bit functions were not properly
> > > > >>> clamping to the maxbit argument at the bit level. They
> > > > >>> were instead only checking maxbit at the byte level.
> > > > >>> To fix this, add a compare and a conditional move
> > > > >>> instruction to the end of the common bit-within-the-
> > > > >>> byte code used by all the functions and be sure not to
> > > > >>> clobber the maxbit argument before it is used.
> > > > >>> 
> > > > >>> Signed-off-by: James Jones <jajones@nvidia.com>
> > > > >>> Tested-by: Stephen Warren <swarren@nvidia.com>
> > > > >> 
> > > > >> Reviewed-by: Nicolas Pitre <nicolas.pitre@linaro.org>
> > > > >> 
> > > > >> Please send to RMK's patch system.
> > > > > 
> > > > > Thanks for the review.  It's already in the patch system, but I updated
> > > > > the entry to include your reviewed-by line.
> > > > 
> > > > Should this be sent to the stable tree too?
> > > 
> > > It could, yes.  This is hardly an urgent fix though, as the bug has been
> > > there virtually forever.
> > > 
> > > 
> > > Nicolas
> > 
> > While ancient, it does cause per-cpu allocations to fail in some situations, 
> > which generally causes panics.
> 
> That would be a good justification for the stable tree then.

And the best way to do that is _not_ to send it to stable@kernel.org,
but when you submit the patch to the patch system, add a line in
the sign-off area:

CC: <stable@kernel.org>

and when it goes into mainline (which is a requirement for stable
patches) the stable team will automatically pick it up - without anyone
needing to do any additional work.

      reply	other threads:[~2010-11-24 19:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12  1:16 [PATCH] ARM: Fix find_next_zero_bit and related assembly James Jones
2010-11-23 21:26 ` Nicolas Pitre
2010-11-23 23:28   ` James Jones
2010-11-24 18:12     ` Stephen Boyd
2010-11-24 19:00       ` Nicolas Pitre
2010-11-24 19:08         ` James Jones
2010-11-24 19:13           ` Nicolas Pitre
2010-11-24 19:15             ` Russell King - ARM Linux [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=20101124191504.GC13934@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=jajones@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@fluxnic.net \
    --cc=sboyd@codeaurora.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