public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Mark Lord <kernel@teksavvy.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Jarod Wilson <jarod@wilsonet.com>
Subject: Re: PATCH: drivers/staging/lirc/lirc_serial.c: use IS_ERR()
Date: Wed, 9 Feb 2011 11:54:43 -0800	[thread overview]
Message-ID: <20110209195443.GA8816@kroah.com> (raw)
In-Reply-To: <20110209195238.GA8707@kroah.com>

On Wed, Feb 09, 2011 at 11:52:38AM -0800, Greg KH wrote:
> On Tue, Feb 08, 2011 at 04:34:39PM -0500, Mark Lord wrote:
> > On 11-02-06 03:39 PM, Mark Lord wrote:
> > > The lirc_serial.c module has never worked with ordinary homebrew
> > > serial blaster hardware, and leaks memory when this is attempted.
> > > 
> > > Fix it by replacing incorrect usage of PTR_ERR() with IS_ERR().
> > > (patch is inline and also attached to bypass mailer issues).
> > > 
> > > Signed-off-by: Mark Lord <mlord@pobox.com>
> > > 
> > > --- linux-2.6.37/drivers/staging/lirc/lirc_serial.c	2011-01-04
> > > 19:50:19.000000000 -0500
> > > +++ linux/drivers/staging/lirc/lirc_serial.c	2011-02-06 15:33:49.854453928 -0500
> > > @@ -966,7 +966,7 @@
> > >  	if (n % sizeof(int) || count % 2 == 0)
> > >  		return -EINVAL;
> > >  	wbuf = memdup_user(buf, n);
> > > -	if (PTR_ERR(wbuf))
> > > +	if (IS_ERR(wbuf))
> > >  		return PTR_ERR(wbuf);
> > >  	spin_lock_irqsave(&hardware[type].lock, flags);
> > >  	if (type == LIRC_IRDEO) {
> > 
> > 
> > Anyone out there?
> > 
> > Greg?
> 
> Patience please, I just got over the flu and am now catching up on
> patches.  I'll go queue this up now.

Actually, it's already fixed in the current tree thanks to Jarod in
commit 88914bdf8c677ebd7e797adac05e47303fd6ac77 so you shouldn't need to
worry about this anymore.

thanks,

greg k-h

      reply	other threads:[~2011-02-09 19:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-06 20:39 PATCH: drivers/staging/lirc/lirc_serial.c: use IS_ERR() Mark Lord
2011-02-08 21:34 ` Mark Lord
2011-02-09 19:52   ` Greg KH
2011-02-09 19:54     ` Greg KH [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=20110209195443.GA8816@kroah.com \
    --to=greg@kroah.com \
    --cc=jarod@wilsonet.com \
    --cc=kernel@teksavvy.com \
    --cc=linux-kernel@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