On 10/17/2017 12:49 AM, Bart Van Assche wrote:
> Use the sgl_alloc_order() and sgl_free_order() functions instead
> of open coding these functions.
>
> Signed-off-by: Bart Van Assche
> Reviewed-by: Johannes Thumshirn
> Cc: linux-s...@vger.kernel.org
> Cc: Martin K. Petersen
> Cc: Anil Ravindran
On 10/17/2017 12:49 AM, Bart Van Assche wrote:
> Signed-off-by: Bart Van Assche
> Reviewed-by: Johannes Thumshirn
> Cc: linux-s...@vger.kernel.org
> Cc: Martin K. Petersen
> Cc: Anil Ravindranath
> ---
> drivers/scsi/pmcraid.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/sc
On 10/17/2017 12:49 AM, Bart Van Assche wrote:
> Use the sgl_alloc_order() and sgl_free_order() functions instead
> of open coding these functions.
>
> Signed-off-by: Bart Van Assche
> Reviewed-by: Johannes Thumshirn
> Cc: linux-s...@vger.kernel.org
> Cc: Martin K. Petersen
> Cc: Brian King
>
On 10/17/2017 12:49 AM, Bart Van Assche wrote:
> Use the sgl_alloc_order() and sgl_free() functions instead of open
> coding these functions.
>
> Signed-off-by: Bart Van Assche
> Cc: Nicholas A. Bellinger
> Cc: Christoph Hellwig
> Cc: Hannes Reinecke
> Cc: Sagi Grimberg
> ---
> drivers/targe
On 10/17/2017 12:49 AM, Bart Van Assche wrote:
> Use the sgl_alloc() and sgl_free() functions instead of open coding
> these functions.
>
> Signed-off-by: Bart Van Assche
> Reviewed-by: Johannes Thumshirn
> Cc: Keith Busch
> Cc: Christoph Hellwig
> Cc: Sagi Grimberg
> ---
> drivers/nvme/targ
On 10/17/2017 12:49 AM, Bart Van Assche wrote:
> Use the sgl_alloc() and sgl_free() functions instead of open coding
> these functions.
>
> Signed-off-by: Bart Van Assche
> Reviewed-by: Johannes Thumshirn
> Cc: Keith Busch
> Cc: Christoph Hellwig
> Cc: James Smart
> Cc: Sagi Grimberg
> ---
>
On 10/17/2017 12:49 AM, Bart Van Assche wrote:
> Many kernel drivers contain code that allocates and frees both a
> scatterlist and the pages that populate that scatterlist.
> Introduce functions in lib/scatterlist.c that perform these tasks
> instead of duplicating this functionality in multiple d
On 10/17/2017 12:49 AM, Bart Van Assche wrote:
> Use the sgl_alloc() and sgl_free() functions instead of open coding
> these functions.
>
> Signed-off-by: Bart Van Assche
> Cc: Ard Biesheuvel
> Cc: Herbert Xu
> ---
> crypto/Kconfig | 1 +
> crypto/scompress.c | 51 ++--
On 17/10/17 01:07, Jonathan Cameron wrote:
So as ever with a linux community focusing on a particular topic, the
obvious solution is a mailing list. There are a number of options on how
do this.
1) Ask one of the industry bodies to host? Who?
2) Put together a compelling argument for linux-a
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly.
Cc: Matt Mackall
Cc: Herbert Xu
Cc: linux-crypto@vger.kernel.org
Signed-off-by: Kees Cook
---
drivers/ch
Tue, Sep 19, 2017 at 11:18:45AM +0800, Herbert Xu wrote:
> Hi:
>
> I have received a report that ghash on ppc64le does not interoperate
> with other implementations of ghash, e.g., on x86-64.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1490972
>
> Could you guys take a look at this and see i
Signed-off-by: Paulo Flabiano Smorigo
---
drivers/crypto/vmx/aes_ctr.c | 33 +
1 file changed, 17 insertions(+), 16 deletions(-)
diff --git a/drivers/crypto/vmx/aes_ctr.c b/drivers/crypto/vmx/aes_ctr.c
index 17d8421..fc60d00 100644
--- a/drivers/crypto/vmx/aes_ctr
Use the sgl_alloc() and sgl_free() functions instead of open coding
these functions.
Signed-off-by: Bart Van Assche
Reviewed-by: Johannes Thumshirn
Cc: Keith Busch
Cc: Christoph Hellwig
Cc: James Smart
Cc: Sagi Grimberg
---
drivers/nvme/target/Kconfig | 1 +
drivers/nvme/target/fc.c| 3
Signed-off-by: Bart Van Assche
Reviewed-by: Johannes Thumshirn
Cc: linux-s...@vger.kernel.org
Cc: Martin K. Petersen
Cc: Anil Ravindranath
---
drivers/scsi/pmcraid.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/scsi/pmcraid.h b/drivers/scsi/pmcraid.h
index 8bfac72a242b..44da91712
Use the sgl_alloc_order() and sgl_free_order() functions instead
of open coding these functions.
Signed-off-by: Bart Van Assche
Reviewed-by: Johannes Thumshirn
Cc: linux-s...@vger.kernel.org
Cc: Martin K. Petersen
Cc: Brian King
---
drivers/scsi/Kconfig | 1 +
drivers/scsi/ipr.c | 49 +
Use the sgl_alloc_order() and sgl_free() functions instead of open
coding these functions.
Signed-off-by: Bart Van Assche
Cc: Nicholas A. Bellinger
Cc: Christoph Hellwig
Cc: Hannes Reinecke
Cc: Sagi Grimberg
---
drivers/target/Kconfig | 1 +
drivers/target/target_core_transp
Use the sgl_alloc() and sgl_free() functions instead of open coding
these functions.
Signed-off-by: Bart Van Assche
Cc: Ard Biesheuvel
Cc: Herbert Xu
---
crypto/Kconfig | 1 +
crypto/scompress.c | 51 ++-
2 files changed, 3 insertions(+), 49
Use the sgl_alloc_order() and sgl_free_order() functions instead
of open coding these functions.
Signed-off-by: Bart Van Assche
Reviewed-by: Johannes Thumshirn
Cc: linux-s...@vger.kernel.org
Cc: Martin K. Petersen
Cc: Anil Ravindranath
---
drivers/scsi/Kconfig | 1 +
drivers/scsi/pmcraid.c
Many kernel drivers contain code that allocates and frees both a
scatterlist and the pages that populate that scatterlist.
Introduce functions in lib/scatterlist.c that perform these tasks
instead of duplicating this functionality in multiple drivers.
Only include these functions in the build if CO
Hello Jens,
As you know there are multiple drivers that both allocate a scatter/gather
list and populate that list with pages. This patch series moves the code for
allocating and freeing such scatterlists from these drivers into
lib/scatterlist.c. Please consider this patch series for kernel v4.15
Use the sgl_alloc() and sgl_free() functions instead of open coding
these functions.
Signed-off-by: Bart Van Assche
Reviewed-by: Johannes Thumshirn
Cc: Keith Busch
Cc: Christoph Hellwig
Cc: Sagi Grimberg
---
drivers/nvme/target/Kconfig | 1 +
drivers/nvme/target/rdma.c | 63 +++
On Mon, Oct 16, 2017 at 03:39:57PM +0530, suni...@techveda.org wrote:
> From: Suniel Mahesh
>
> This fixes the following coccinelle warning:
> WARNING: return of 0/1 in function 'ssi_is_hw_key' with return type bool.
Perhaps
Coccinelle emits WARNING: return of 0/1 in function 'ssi_is_hw_key' wi
On Mon, Oct 16, 2017 at 03:38:11PM +0530, suni...@techveda.org wrote:
> From: Suniel Mahesh
>
> Bool tests don't need comparisons.
This commit log could be a bit longer. You may like to read
Documentation/process/submitting-patches.rst (section 2).
> This fixes the following coccinelle warning:
Am Montag, 16. Oktober 2017, 08:53:00 CEST schrieb Christophe LEROY:
Hi Christophe,
> Hi Stephan,
>
> I get an issue with md5sum of a big file with kernel 4.9. It don't get
> that issue with kernel 4.13.
The key to the difference in libkcapi is the following code:
static void _kcapi_handle_fla
Hi all,
sorry for error in subject line, it should be [PATCH v6 0/2] and so on,
I can resend this if needed ?
On 16.10.2017 19:43, Kamil Konieczny wrote:
> First patch cleans up spaces in defines, second adds HASH support for Exynos.
> Changes:
--
Best regards,
Kamil Konieczny
Samsung R&D Insti
Add support for MD5, SHA1, SHA256 hash algorithms for Exynos HW.
It uses the crypto framework asynchronous hash api.
It is based on omap-sham.c driver.
S5P has some HW differencies and is not implemented.
Modifications in s5p-sss:
- Add hash supporting structures and functions.
- Modify irq hand
Change spaces into tabs in defines.
Signed-off-by: Kamil Konieczny
---
drivers/crypto/s5p-sss.c | 190 +++
1 file changed, 95 insertions(+), 95 deletions(-)
diff --git a/drivers/crypto/s5p-sss.c b/drivers/crypto/s5p-sss.c
index 7ac657f46d15..dfae1865c
First patch cleans up spaces in defines, second adds HASH support for Exynos.
Changes:
version 6:
- fixes suggested by Vladimir Zapolskiy: change HASH_OP enum into bool, fix
comments, change int into unsigned int in several functions, change some
functions to return void, remove unnecessary pa
Hello Vladimir,
>>[snip]
>> -static struct s5p_aes_dev *s5p_dev;
>> +enum hash_op {
>> +HASH_OP_UPDATE = 1,
>> +HASH_OP_FINAL = 2
>> +};
>
> If this type is not going to be extended, then I'd rather suggest to
> use a boolean correspondent field in the struct s5p_hash_reqctx instead
> of
Hello Vladimir,
thank you for review. I will apply most of your suggestions,
in a few places it is not possible, see comments below.
Your review helped me to improve two functions.
On 12.10.2017 13:45, Vladimir Zapolskiy wrote:
> Hello Kamil,
>
> thank you for the change, please find below a num
struct sha256_ctx_mgr allocated in sha256_mb_mod_init() via kzalloc()
and later passed in sha256_mb_flusher_mgr_flush_avx2() function where
instructions vmovdqa used to access the struct. vmovdqa requires
16-bytes aligned argument, but nothing guarantees that struct
sha256_ctx_mgr will have that al
struct sha1_ctx_mgr allocated in sha1_mb_mod_init() via kzalloc()
and later passed in sha1_mb_flusher_mgr_flush_avx2() function where
instructions vmovdqa used to access the struct. vmovdqa requires
16-bytes aligned argument, but nothing guarantees that struct
sha1_ctx_mgr will have that alignment.
> > So as ever with a linux community focusing on a particular topic, the
> > obvious solution is a mailing list. There are a number of options on how
> > do this.
> >
> > 1) Ask one of the industry bodies to host? Who?
> >
> > 2) Put together a compelling argument for linux-accelerat...@vger.k
From: Suniel Mahesh
This fixes the following coccinelle warning:
WARNING: return of 0/1 in function 'ssi_is_hw_key' with return type bool.
Signed-off-by: Suniel Mahesh
---
Note:
- Patch was tested and built(ARCH=arm) on latest
linux-next.
- No build issues reported, however it was not
teste
From: Suniel Mahesh
Bool tests don't need comparisons.
This fixes the following coccinelle warning:
WARNING: Comparison of bool to 0/1
Signed-off-by: Suniel Mahesh
---
Note:
- Patch was tested and built(ARCH=arm) on latest
linux-next.
- No build issues reported, however it was not
tested o
35 matches
Mail list logo
