linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
	Ondrej Kozina <okozina@redhat.com>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [PATCH] avoid excessive use of socket buffer in skcipher
Date: Sat, 08 Nov 2014 09:44:02 +0100	[thread overview]
Message-ID: <545DD7D2.4010006@gmail.com> (raw)
In-Reply-To: <20140904070852.GA2606@gondor.apana.org.au>

On 09/04/2014 09:08 AM, Herbert Xu wrote:
> On Mon, Aug 25, 2014 at 11:49:54AM +0200, Ondrej Kozina wrote:
>> On archs with PAGE_SIZE >= 64 KiB the function skcipher_alloc_sgl()
>> fails with -ENOMEM no matter what user space actually requested.
>> This is caused by the fact sock_kmalloc call inside the function tried
>> to allocate more memory than allowed by the default kernel socket buffer
>> size (kernel param net.core.optmem_max).
>>
>> Signed-off-by: Ondrej Kozina <okozina@redhat.com>
> 
> Patch applied.  Thanks!

Please could you send this also to stable tree?
Upstream commit now is e2cffb5f493a8b431dc87124388ea59b79f0bccb

I think it is the problem in all kernels using large page size and skcipher api.

Thanks,
Milan

  reply	other threads:[~2014-11-08  8:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-25  9:49 [PATCH] avoid excessive use of socket buffer in skcipher Ondrej Kozina
2014-08-25  9:49 ` Ondrej Kozina
2014-09-01 15:22   ` Ondrej Kozina
2014-09-01 15:42     ` Ondrej Kozina
2014-09-04  7:08   ` Herbert Xu
2014-11-08  8:44     ` Milan Broz [this message]
     [not found] <1408960085-11583-1-git-send-email-okozina@redhat.com>
2014-08-25  9:48 ` Ondrej Kozina

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=545DD7D2.4010006@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=okozina@redhat.com \
    /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).