public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Richard Purdie <rpurdie@linux.intel.com>,
	akpm <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, kernel@pengutronix.de,
	stable@kernel.org
Subject: Re: [stable] [PATCH] backlight: grab ops_lock before testing bd->ops
Date: Mon, 22 Nov 2010 09:53:32 -0800	[thread overview]
Message-ID: <20101122175332.GC18808@kroah.com> (raw)
In-Reply-To: <20101122100532.GA4693@pengutronix.de>

On Mon, Nov 22, 2010 at 11:05:32AM +0100, Uwe Kleine-König wrote:
> Hello,
> 
> On Mon, Nov 22, 2010 at 09:59:07AM +0000, Richard Purdie wrote:
> > On Mon, 2010-11-22 at 10:43 +0100, Uwe Kleine-König wrote:
> > > According to the comment describing ops_lock in the definition of
> > > struct backlight_device and when comparing with other functions in
> > > backlight.c the mutex must be hold when checking ops to be non-NULL.
> > > 
> > > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > 
> > Acked-by: Richard Purdie <rpurdie@linux.intel.com>
> The problem was introduced by c835ee7f4154992e6cf0674d7ee136f5d36247a4
> (that is in 2.6.29-rc1).  Is this relevant for stable?

Yes.

What is the git commit id of the fix in Linus's tree?

thanks,

greg k-h

  reply	other threads:[~2010-11-22 18:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22  9:43 [PATCH] backlight: grab ops_lock before testing bd->ops Uwe Kleine-König
2010-11-22  9:59 ` Richard Purdie
2010-11-22 10:05   ` Uwe Kleine-König
2010-11-22 17:53     ` Greg KH [this message]
2010-11-23  8:56       ` [stable] " Uwe Kleine-König

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=20101122175332.GC18808@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpurdie@linux.intel.com \
    --cc=stable@kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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