From: David Miller <davem@davemloft.net>
To: dhowells@redhat.com
Cc: netdev@vger.kernel.org, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] rxrpc: Don't put crypto buffers on the stack
Date: Thu, 08 Feb 2018 13:48:47 -0500 (EST) [thread overview]
Message-ID: <20180208.134847.2294397519191048232.davem@davemloft.net> (raw)
In-Reply-To: <151810554726.19320.4571236293389358221.stgit@warthog.procyon.org.uk>
From: David Howells <dhowells@redhat.com>
Date: Thu, 08 Feb 2018 15:59:07 +0000
> Don't put buffers of data to be handed to crypto on the stack as this may
> cause an assertion failure in the kernel (see below). Fix this by using an
> kmalloc'd buffer instead.
...
> Reported-by: Jonathan Billings <jsbillings@jsbillings.org>
> Reported-by: Marc Dionne <marc.dionne@auristor.com>
> Signed-off-by: David Howells <dhowells@redhat.com>
> Tested-by: Jonathan Billings <jsbillings@jsbillings.org>
Applied, thanks David.
prev parent reply other threads:[~2018-02-08 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 15:59 [PATCH net] rxrpc: Don't put crypto buffers on the stack David Howells
2018-02-08 18:48 ` David Miller [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=20180208.134847.2294397519191048232.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).