archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <>
To: Samuel Ortiz <>,
	"David S. Miller" <>
	Dan Carpenter <>,
	Johan Hovold <>, stable <>,
	Greg Kroah-Hartman <>,,
	Andrew Morton <>,
	Ben Hutchings <>
Subject: Re: [PATCH] NFC: fix device-allocation error return
Date: Mon, 28 Aug 2017 10:39:12 +0200	[thread overview]
Message-ID: <20170828083912.GB20634@localhost> (raw)
In-Reply-To: <20170722133228.GE2729@localhost>

Samuel or David,

On Sat, Jul 22, 2017 at 03:32:28PM +0200, Johan Hovold wrote:
> On Sun, Jul 09, 2017 at 01:08:58PM +0200, Johan Hovold wrote:
> > A recent change fixing NFC device allocation itself introduced an
> > error-handling bug by returning an error pointer in case device-id
> > allocation failed. This is clearly broken as the callers still expected
> > NULL to be returned on errors as detected by Dan's static checker.
> > 
> > Fix this up by returning NULL in the event that we've run out of memory
> > when allocating a new device id.
> > 
> > Note that the offending commit is marked for stable (3.8) so this fix
> > needs to be backported along with it.
> > 
> > Fixes: 20777bc57c34 ("NFC: fix broken device allocation")
> > Cc: stable <>	# 3.8
> > Reported-by: Dan Carpenter <>
> > Signed-off-by: Johan Hovold <>

> Could you apply this follow-up fix so that it can be backported along
> with the offending commit (which was just added to the stable queues)?
> We would only hit this error path if an ida allocation fails due to OOM;
> so while this is not critical, it would still be nice to get it fixed.

Another reminder about this one; can you apply it so we can get it into

Note that the offending commit has now been backported to the stable
trees and we really want this trivial follow-up fix to be backported as

Let me know if you want me to resend the patch.


  reply	other threads:[~2017-08-28  8:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-09 11:08 [PATCH] NFC: fix device-allocation error return Johan Hovold
2017-07-22 13:32 ` Johan Hovold
2017-08-28  8:39   ` Johan Hovold [this message]
2017-11-05 23:54 ` Samuel Ortiz

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170828083912.GB20634@localhost \ \ \ \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).