From: Marek Vasut <marex@denx.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Horia Geanta <horia.geanta@freescale.com>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, stable@vger.kernel.org,
Kim Phillips <kim.phillips@freescale.com>
Subject: Re: [PATCH crypto 2/2] crypto: caam - add allocation failure handling in SPRINTFCAT macro
Date: Mon, 28 Apr 2014 21:28:41 +0200 [thread overview]
Message-ID: <201404282128.41302.marex@denx.de> (raw)
In-Reply-To: <20140428102441.GA17037@gondor.apana.org.au>
On Monday, April 28, 2014 at 12:24:41 PM, Herbert Xu wrote:
> On Fri, Apr 18, 2014 at 01:01:42PM +0300, Horia Geanta wrote:
> > GFP_ATOMIC memory allocation could fail.
> > In this case, avoid NULL pointer dereference and notify user.
> >
> > Cc: <stable@vger.kernel.org> # 3.2+
> > Cc: Kim Phillips <kim.phillips@freescale.com>
> > Signed-off-by: Horia Geanta <horia.geanta@freescale.com>
>
> Patch applied to the crypto tree. Thanks.
Hi Herbert,
Don't you instead want to apply my 11-patch series from
Message-Id: <1398362722-16430-1-git-send-email-marex@denx.de>
Subject: [PATCH 00/11] crypto: caam: Error reporting fixes
which actually fixes this SPRINTFCAT() horror properly please ?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-04-28 21:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 10:01 [PATCH crypto 1/2] crypto: caam - fix mem leak in ahash_setkey Horia Geanta
2014-04-18 10:01 ` [PATCH crypto 2/2] crypto: caam - add allocation failure handling in SPRINTFCAT macro Horia Geanta
2014-04-22 23:56 ` Marek Vasut
2014-04-23 16:35 ` Horia Geantă
2014-04-23 17:12 ` Marek Vasut
2014-04-23 17:41 ` Marek Vasut
2014-04-28 10:24 ` Herbert Xu
2014-04-28 19:28 ` Marek Vasut [this message]
2014-04-28 21:53 ` Herbert Xu
2014-04-28 22:29 ` Marek Vasut
2014-04-22 23:47 ` [PATCH crypto 1/2] crypto: caam - fix mem leak in ahash_setkey Marek Vasut
2014-04-28 10:25 ` Herbert Xu
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=201404282128.41302.marex@denx.de \
--to=marex@denx.de \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@freescale.com \
--cc=kim.phillips@freescale.com \
--cc=linux-crypto@vger.kernel.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.