On 07/03/2017 06:44 AM, Renesanso wrote:
> Hi for all.
>
> Dmitry Kasatkin's fork of linux.git write dm-integrity patch for linux
...
yes, unfortunately we named the target the same (and I realized it too late).
It is doing something similar but definitely it is not the same.
> I try to use
On Mon, Jul 3, 2017 at 3:35 PM, Herbert Xu wrote:
> On Sun, Jul 02, 2017 at 05:41:43PM +0300, Gilad Ben-Yossef wrote:
>> The crypto API was using the -EBUSY return value to indicate
>> both a hard failure to submit a crypto operation into a
>> transformation provider
On Sun, Jul 02, 2017 at 05:41:43PM +0300, Gilad Ben-Yossef wrote:
> The crypto API was using the -EBUSY return value to indicate
> both a hard failure to submit a crypto operation into a
> transformation provider when the latter was busy and the backlog
> mechanism was not enabled as well as a
Hi Bian,
On Sat, Jul 1, 2017 at 2:33 AM, Brian King wrote:
> On 06/30/2017 09:08 AM, Jens Axboe wrote:
> Compared with the totally percpu approach, this way might help 1:M or
> N:M mapping, but won't help 1:1 map(NVMe), when hctx is mapped to
> each
The code sample is waiting for an async. crypto op completion.
Adapt sample to use the new generic infrastructure to do the same.
This also fixes a possible data coruption bug created by the
use of wait_for_completion_interruptible() without dealing
correctly with an interrupt aborting the wait
Replace -EBUSY with -EIOCBQUEUED for backlog queueing indication
as part of new API.
Signed-off-by: Gilad Ben-Yossef
---
This patch should be squashed with the first patch in the series
when applied.
Documentation/crypto/api-samples.rst | 2 +-
1 file changed, 1
A zone ID is a 32 bits unsigned int which can overflow when doing the
bit shifts calculations in dmz_start_sect(). With a 256 MB zone size
drive, the overflow happens for a zone ID >= 8192.
Fix this by casting the zone ID to a sector_t before doing the bit
shift. While at it, similarly fix