Re: KASAN: use-after-free Read in __list_del_entry_valid (2)

Am Montag, 18. Dezember 2017, 06:50:01 CET schrieb syzbot: Hi, > Hello, > > syzkaller hit the following crash on > 82bcf1def3b5f1251177ad47c44f7e17af039b4b > git://git.cmpxchg.org/linux-mmots.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console output is attached.

Re: BUG: unable to handle kernel NULL pointer dereference in __crypto_alg_lookup

Am Montag, 18. Dezember 2017, 06:50:01 CET schrieb syzbot: Hi, > Hello, > > syzkaller hit the following crash on > 41d8c16909ebda40f7b4982a7f5e2ad102705ade > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw

(brak tematu)

-- Wir bieten Kredite an alle in Not mit 3% Zinssatz, keine Sicherheiten beteiligt, überprüfen wir nicht auch Kredit-Scores, erhalten schnelle und zuverlässige Darlehen innerhalb von 3 Tagen garantieren. E-Mail jetzt für weitere Informationen.

Re: [PATCH v2] hwrng: Clean up RNG list when last hwrng is unregistered

On 17 December 2017 at 14:53, PrasannaKumar Muralidharan wrote: > Hi Gary, > > Some minor comments below. > > On 16 December 2017 at 01:25, Gary R Hook wrote: >> >> Commit 142a27f0a731 added support for a "best" RNG, and in doing so >> introduced a hang from rmmod/modprobe -r when the last RNG on

Re: [PATCH v2] hwrng: Clean up RNG list when last hwrng is unregistered

Hi Gary, Some minor comments below. On 16 December 2017 at 01:25, Gary R Hook wrote: > > Commit 142a27f0a731 added support for a "best" RNG, and in doing so > introduced a hang from rmmod/modprobe -r when the last RNG on the list > was unloaded. Nice catch. Thanks for fixing this. > When the h

[PATCH v2 3/6] crypto: tcrypt: allow setting num of bufs

For multiple buffers speed tests, the number of buffers, or requests, used actually sets the level of parallelism a tfm provider may utilize to hide latency. The existing number (of 8) is good for some software based providers but not enough for many HW providers with deep FIFOs. Add a module para

[PATCH v2 4/6] crypto: tcrypt: add multi buf ahash jiffies test

The multi buffer concurrent requests ahash speed test only supported the cycles mode. Add support for the so called jiffies mode that test performance of bytes/sec. We only add support for digest mode at the moment. Signed-off-by: Gilad Ben-Yossef --- crypto/tcrypt.c | 112 +

[PATCH v2 6/6] crypto: tcrypt: add multibuf aead speed test

The performance of some aead tfm providers is affected by the amount of parallelism possible with the processing. Introduce an async aead concurrent multiple buffer processing speed test to be able to test performance of such tfm providers. Signed-off-by: Gilad Ben-Yossef --- crypto/tcrypt.c |

[PATCH v2 0/6] crypto: tcrypt: fix and add multi buf speed tests

The performance of some crypto tfm providers is affected by the amount of parallelism possible with the processing. We already had some support for speed test of multiple concurrent requests, dubbed multi buffer, in ahash speed tests.

[PATCH v2 5/6] crypto: tcrypt: add multibuf skcipher speed test

The performance of some skcipher tfm providers is affected by the amount of parallelism possible with the processing. Introduce an async skcipher concurrent multiple buffer processing speed test to be able to test performance of such tfm providers. Signed-off-by: Gilad Ben-Yossef --- crypto/tcr

[PATCH v2 2/6] crypto: tcrypt: fix AEAD decryption speed test

The AEAD speed test pretended to support decryption, however that support was broken as decryption requires a valid auth field which the test did not provide. Fix this by running the encryption path once with inout/output sgls switched to calculate the auth field prior to performing decryption spe

[PATCH v2 1/6] crypto: tcrypt: use multi buf for ahash mb test

The multi buffer ahash speed test was allocating multiple buffers for use with the multiple outstanding requests it was starting but never actually using them (except to free them), instead using a different single statically allocated buffer for all requests. Fix this by actually using the alloca