Sorry for resend this email, just add the linux-crypto@vger.kernel.org
and linux-ker...@vger.kernel.org.
Hi,
Firstly, thanks for your reply!
To reproduce this kernel panic, I test the encryption/decryption feature
on arm64 board with more memory. Just add the following
change:
diff --gi
Sorry for noise!
--
Regards
Kaixu Xia
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Sep 08, 2016 at 05:47:13PM +0200, Romain Perier wrote:
>
> I was wondering something. hwrng_unregister does not check the kref
> reference counter of the object... so technically if the current
> rng_device is in use, with or without devm... calling
> platform->remove will break the driver
Am Donnerstag, 8. September 2016, 04:52:08 CEST schrieb Stephan Mueller:
Hi,
> Hi Herbert,
>
> another one, different than the first report
Please note that the error seems to be triggered due to a bad use of the user
space interface: When submitting the iov, I told the kernel that iovlen is t
Le 07/09/2016 16:45, PrasannaKumar Muralidharan a écrit :
On 7 September 2016 at 19:53, Romain Perier
wrote:
Hello,
Le 06/09/2016 18:31, PrasannaKumar Muralidharan a écrit :
Use devm_hwrng_register instead of hwrng_register. It avoids the need
to handle unregistration explicitly from the
A merge conflict between the akpm-current tree and the crypto tree
caused a build failure in ARM allmodconfig today:
crypto/crypto_engine.c: In function 'crypto_transfer_hash_request':
crypto/crypto_engine.c:234:3: error: implicit declaration of function
'queue_kthread_work' [-Werror=implicit-fun
On Thu, Sep 08, 2016 at 08:38:43PM +0800, xiakaixu wrote:
> Hi,
>
> I am using the encryption/decryption feature on arm64 board and a kernel
> panic occurs just when open a file. As the memory size of the board
> is limited
> and there are some page allocation failures before the panic.
>
> Seem
On Thu, Sep 08, 2016 at 03:17:46PM +0530, Harsh Jain wrote:
> Hi,
>
> What is the expected behavior when driver is unregistered(Rmmod ) with
> active ipsec session.?
> I am getting stacktrace(BUG_ON in crypto_unregister_alg) instead of
> "module in use".
The driver is supposed to set cra_module t
Hi,
What is the expected behavior when driver is unregistered(Rmmod ) with
active ipsec session.?
I am getting stacktrace(BUG_ON in crypto_unregister_alg) instead of
"module in use".
Regards
Harsh Jain
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a me
