On Mon, 29 Oct 2018 09:50:13 +, Gilad Ben-Yossef wrote:
> Add device tree bindings associating Arm TrustZone CryptoCell 713 with the
> ccree driver.
>
> Signed-off-by: Gilad Ben-Yossef
> ---
> Documentation/devicetree/bindings/crypto/arm-cryptocell.txt | 7 +--
> 1 file changed, 5 insert
On 2018/10/30 22:03, Benjamin Coddington wrote:
> On 30 Oct 2018, at 9:58, zhong jiang wrote:
>
>> On 2018/10/30 21:06, Benjamin Coddington wrote:
>>> Hi zhong jiang,
>>>
>>> Try asking in linux-nfs.. but I'll also note that 3.10-stable may be
>>> missing a number of fixes to leaks in the NFS GSS c
On 30 Oct 2018, at 9:58, zhong jiang wrote:
> On 2018/10/30 21:06, Benjamin Coddington wrote:
>> Hi zhong jiang,
>>
>> Try asking in linux-nfs.. but I'll also note that 3.10-stable may be
>> missing a number of fixes to leaks in the NFS GSS code.
>>
>> I can see a more than a few fixes to memory l
On 2018/10/30 21:06, Benjamin Coddington wrote:
> Hi zhong jiang,
>
> Try asking in linux-nfs.. but I'll also note that 3.10-stable may be missing
> a number of fixes to leaks in the NFS GSS code.
>
> I can see a more than a few fixes to memory leaks with:
> git log --grep=leak --oneline net/sunrp
Hi zhong jiang,
Try asking in linux-nfs.. but I'll also note that 3.10-stable may be
missing a number of fixes to leaks in the NFS GSS code.
I can see a more than a few fixes to memory leaks with:
git log --grep=leak --oneline net/sunrpc/auth_gss/
Ben
On 30 Oct 2018, at 8:45, zhong jiang wro
Hi, Herbert
Recently, I hit a memory leak issue when mounting and unmounting nfs with
the way of krb5.
The issue happens to the linux-3.10-stable.
I find that slab-1024 and slab-512 will take up most of the memory. And it can
not be freed.
Meanwhile, it result in rpcsec_gss_krb5 can be
From: Colin Ian King
Trivial fix to clean up varous indentation issue
Signed-off-by: Colin Ian King
---
drivers/crypto/chelsio/chcr_algo.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/crypto/chelsio/chcr_algo.c
b/drivers/crypto/chelsio/chcr_algo
Hi Wenwen,
Thanks for the patch. We can't think of any such scenarios,
where our device can corrupt meta data of the given context pointer as per our
usage in the device.
But having meta data in separate pointer prevents unexpected behavior.
Thanks
srikanth
_
On Wed, Oct 24, 2018 at 03:06:17PM -0700, Eric Biggers wrote:
>
> The patch I've been using just exposes a file /proc/cryptobench (note: it
> maybe
> should be made into a char device instead) to which you can write commands
> like:
>
> algtype=skcipher algname=adiantum(xchacha12,aes) keys
